Human approval
A step_up decision freezes one exact ActionRequest for review. Approval is not a background job and does not authorize similar future actions.
Configure an approval flow
Section titled “Configure an approval flow”Give the flow a stable key and bounded expiry. Select eligible approvers from exact tenant User emails, current tenant directory groups, or the current Workspace administrator role. Any one eligible approver can resolve the single gate; the first valid approve or deny decision wins.
Then reference the flow from a step_up authorization policy. If matching rules select different flows, Axec denies instead of choosing one.
Review safely
Section titled “Review safely”The approval view exposes an allowlisted projection: identities, Application and gateway, Connector, capability or normalized proxy target, caller reason, matched policy, status, and timing. It does not expose raw MCP arguments, proxy headers, query values, request bodies, or credentials.
An approval moves the request only to approved. A denial is terminal. Expiry never auto-approves.
Poll, then retry
Section titled “Poll, then retry”The requesting principal may poll the ActionRequest for non-secret status and expiry. Polling never executes or releases anything.
After approval, retry with:
- the same authenticated subject, client, optional workload actor, gateway, and operation scope
- the same Grant and usage, Connector, capability or target
- identical canonical arguments or credential selector
- the original ActionRequest identifier and idempotency binding
- fresh confidential Application proof for credential release
Axec reloads live authority and current policy before execution. Current deny, a different step-up flow, expired approval, revoked authority, or changed Connector contract prevents continuation. A matching current flow can consume the frozen approval.
Handle completion states
Section titled “Handle completion states”Only one retry can atomically claim approved to executing. Concurrent retries receive current state or the stored result. If a mutating operation may have reached upstream but its outcome is unclear, Axec returns outcome_unknown and does not dispatch it again; reconcile with a safe read operation. An ambiguous credential delivery requires a new governed release request.
Use the ActionRequest receipt to trace acceptance, policy, approval, dispatch, and terminal state.