Approvals

Hold a tool call for review and resume the exact approved request safely.

An ask policy creates a durable approval request before the provider is called. The execution remains awaiting_approval and returns a receipt:

{
  "id": "execution-uuid",
  "actionVersion": "1",
  "status": "awaiting_approval",
  "result": null,
  "error": "approval_required",
  "approvalId": "approval-uuid",
  "replayed": false
}

Review and decide

Open the approval in the dashboard and inspect the exact action, version, arguments, acting user and selected access source. Direct users can review their own requests. An authorized business administrator can review requests in the selected project. The preview is authenticated, is not cached, and never includes stored provider credentials.

Approve only the specific request you intend to run. Denying it ends that execution without a provider call. Requests expire after 24 hours if they have not been consumed. The dashboard records who decided and when.

Safe resumption

Approval queues the existing execution for the worker. The agent does not need to issue a new execution. Poll the receipt with get_execution over MCP or getExecution in the TypeScript client.

Before dispatch, Arc0 checks current caller authority, policy revision, subject, tool version, connection or access source, and the original request digest. A changed policy, revoked key, disabled tool, changed account or expired approval prevents execution. Concurrent decisions and duplicate jobs cannot dispatch the same execution twice.

The approval authorizes the sealed original arguments. Changing the arguments requires a new request and a new approval. A successful provider call is not repeated when the agent retries with the same idempotency key.

Provider timeouts can still leave an uncertain external outcome. Approval does not make an external write reversible; reconcile the result before issuing another request.

A server-held business key can list approvals and inspect their sealed original requests through GET /v1/approvals and GET /v1/approvals/:approvalId with approvals:read. POST /v1/approvals/:approvalId/decision requires approvals:decide and {decision: "approve" | "deny"}. Use Idempotency-Key when submitting a decision. These routes are limited to the key's project; user-bound runtime keys cannot call them. Your application must obtain the human's decision; a coding agent must never approve automatically. See the API reference.

Email approval buttons and configurable approval routing are not part of the current implementation. Connection-health notifications are a separate feature. See Policies and Arc0 MCP.

On this page