Cancel all open orders.
AI agents call cancel_all_orders to permanently remove resources in Alpaca MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling all open orders is a destructive action that cannot be undone—it permanently revokes all pending trades. While not directly a financial transaction, it has severe financial consequences by eliminating positions the user intended to execute. The blast radius is critical because an AI agent could cancel a user's entire trading strategy in one action, causing significant financial harm.
From the tool's definition Tool name explicitly states "cancel_all_orders" and description states "Cancel all open orders." This irreversibly cancels all pending trading orders without any undo capability.
Attacks that exploit this kind of access
Cancel all open orders. It is categorised as a Destructive tool in the Alpaca MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Alpaca MCP Server MCP server in PolicyLayer and add a rule for cancel_all_orders: 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 Alpaca MCP Server. Nothing to install.
cancel_all_orders 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 cancel_all_orders 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 cancel_all_orders. 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.
cancel_all_orders is provided by the Alpaca MCP Server MCP server (miguelyad26/alpaca-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →