Approve a pending agent decision after explicit user confirmation. Also known as: sign off, approve AI work, unblock agent, accept decision. USE WHEN: user says to approve a decision returned from list_entities with type=decision and status=pending (or the legacy get_pending_decisions alias). NEX...
AI agents use approve_decision to create or update resources in OrgX — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OrgX environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | — | Optional note recorded with the approval |
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
option_id | string | — | Optional decision option id when the decision includes selectable options. |
decision_id | string | — | Decision ID to approve |
Parameters from the server's own tool schema.
An AI agent can call approve_decision faster than any human can review — one bad instruction and it creates or modifies resources in OrgX by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (20 properties)
Documented attack patterns abuse exactly the kind of access approve_decision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OrgX, and nothing reaches the server without passing your rules. This is the rule we recommend for approve_decision:
{
"version": "1",
"default": "deny",
"tools": {
"approve_decision": {
"limits": [
{
"counter": "approve_decision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}approve_decision stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Approve a pending agent decision after explicit user confirmation. Also known as: sign off, approve AI work, unblock agent, accept decision. USE WHEN: user says to approve a decision returned from list_entities with type=decision and status=pending (or the legacy get_pending_decisions alias). NEXT: Confirm approval to user; agent is notified automatically. DO NOT USE: without showing the decision to the user first. Requires decisions:write. It is categorised as a Write tool in the OrgX MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
approve_decision accepts 4 parameters: note, _context, option_id, decision_id. The full parameter table on this page comes from the server's own tool schema.
Register the OrgX MCP server in PolicyLayer and add a rule for approve_decision: 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 OrgX. Nothing to install.
approve_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the approve_decision 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 approve_decision. 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.
approve_decision is provided by the OrgX MCP server (useorgx/orgx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 OrgX tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 OrgX tools catalogued and risk-classified — across an index of 42,500+ MCP servers.