Core concepts / Approvals

Approvals

Park a tool call before it reaches an upstream, then let an operator decide.

How a call waits

Ask-first policy is configured on a connector for a specific connection and bare tool name. The tool must also be exposed by that connector. Synaxis records the proposed arguments and blocks the MCP call until approval, denial, or timeout.

Decision and delivery

The approval decision is durable and the waiting Engine polls for it, but the original in-flight request remains local to that process. A restart never replays the upstream action. Operators see the request in the console and Engine logs; an outbound notification is sent only when ALERT_WEBHOOK_URL is configured.

Use approvals deliberately

Approval is not a substitute for curation. A destructive tool you never need should not be exposed at all.