decide_approval
Answer a waiting checkpoint by request id: approve, reject, or amend. 'amend' means send the step back to be redone with the change described in notes, so notes are required for it. Spends money: approve continues the run and amend re-runs the step, both billed. Fails with a clear error, rather t...
This record as markdown: /tools/com-meta-council-decision-intelligence/decide-approval.md
What decide_approval does on Meta Council
AI agents call decide_approval to permanently remove resources in Meta Council, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | What you want changed or why. Required when decision is amend; optional otherwise. |
decision | string | Yes | approve continues the run; reject sends the step back to be redone; amend does the same but requires notes saying what to change. |
approval_id | string | Yes | The request's id, from list_approvals. |
Parameters from the server's own tool schema.
Why decide_approval is rated Critical
An AI agent that decides to call decide_approval doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Meta Council is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs decide_approval safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For decide_approval, this is the rule to start with:
decide_approval is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every decide_approval call is checked against it from then on.
Questions about decide_approval
Answer a waiting checkpoint by request id: approve, reject, or amend. 'amend' means send the step back to be redone with the change described in notes, so notes are required for it. Spends money: approve continues the run and amend re-runs the step, both billed. Fails with a clear error, rather than silently doing nothing, if the run is no longer waiting. Requires authentication and the workflows:approve scope. It is categorised as a Destructive tool in the Meta Council MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
decide_approval accepts 3 parameters: notes, decision, approval_id. Required: decision, approval_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for decide_approval: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Meta Council. Nothing to install.
decide_approval is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the decide_approval rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for decide_approval. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
decide_approval is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
Across the catalogue