Approve an exact write

Every tool write requires a human decision. An agent cannot turn this off, invent approval, or use a service actor to approve its own work. Financial execution is excluded from the pilot.

Show the proposed operation

When a run enters requires_action, retrieve its approval using an authorized user context. Show the destination, operation, and exact proposed input. The approval binds the run, actor, input hash, immutable tool revision, and connector generation. Any change invalidates the old decision.

Your backend authenticates the human action and submits the decision using separately granted approval:delegate authority. Console administrator roles do not automatically grant access to end-user content or approval rights.

curl --fail-with-body "$MYSTRO_SCOPE/approvals/apr_example/decision" \
  -H "Authorization: Bearer $MYSTRO_APPROVAL_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: approve-op-example-001' \
  --data '{"decision":"approve"}'

deny is also valid. A decision expires after ten minutes; replay or an expired token cannot authorize a new operation. While waiting, the run persists its continuation and releases compute. Resume does not repeat already completed tools.

Recheck at execution

Mystro checks current grants and revocation before dispatch. Your endpoint checks live domain access before committing. If the user loses access, the connection is revoked, or the tool changes after the screen was shown, fail closed and present the updated state. Approval is permission to attempt the exact action, not a guarantee it succeeded.