Apply a workflow Decision to a specific order (POST /v3/accounts/{account_id}/users/{user_id}/orders/{order_id}/decisions). Order-level decisions target a single transaction rather than the whole user (e.g.
AI agents invoke apply_decision_to_order to trigger actions in Mcp Ap2. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a workflow decision against a specific order/transaction. It is not merely reading or writing data — it triggers an operational workflow action (decision engine) that can alter the state of a financial transaction. While it touches financial orders, its primary action is executing a workflow decision rather than directly moving money, placing it in Execute.
From the tool's definition 'Apply a workflow Decision to a specific order' via POST to /orders/{order_id}/decisions — triggers an external workflow decision on a transaction
Documented attack patterns abuse exactly the kind of access apply_decision_to_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for apply_decision_to_order:
{
"version": "1",
"default": "deny",
"tools": {
"apply_decision_to_order": {
"limits": [
{
"counter": "apply_decision_to_order_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}apply_decision_to_order stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Apply a workflow Decision to a specific order (POST /v3/accounts/{account_id}/users/{user_id}/orders/{order_id}/decisions). Order-level decisions target a single transaction rather than the whole user (e.g. It is categorised as a Execute tool in the Mcp Ap2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for apply_decision_to_order: 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 Mcp Ap2. Nothing to install.
apply_decision_to_order is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the apply_decision_to_order 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 apply_decision_to_order. 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.
apply_decision_to_order is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.