Approvals decide when a tool call must pause for a human decision. They are configured on the same fleet and agent configuration surface as tools and instructions. Approval policy keys use the same naming style as tools. You can gate one exact tool, such asDocumentation Index
Fetch the complete documentation index at: https://docs.cerca.dev/llms.txt
Use this file to discover all available pages before exploring further.
sandbox.exec; a namespace wildcard, such as docs.*; or everything with *. When multiple keys match, the most specific one wins, so a broad fleet-level rule can be tightened or relaxed for a single tool without rewriting the rest.
Fleet defaults and agent overrides are merged per approval key unless the fleet locks approvals. That lets an operator add a new fleet-level gate without rewriting every agent.
Use approvals for actions with side effects: sending email, writing to production systems, running commands, changing approval policy, or calling custom tools that mutate customer data.
To react to approval activity from your own product, subscribe to the approval.requested, approval.resolved, and approval.granted webhook events.