Cancels an existing pending order.
AI agents call cancel_order_tool to permanently remove resources in Alpaca MCP Gold Standard — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a pending order is an irreversible action in the context of order execution — once cancelled, the order no longer exists and cannot be reinstated. In a trading context, this can have significant financial consequences (e.g., missing a desired entry/exit point), and the cancellation itself cannot be undone. This falls under Destructive as the operation permanently removes the order from the system.
From the tool's definition Cancels an existing pending order
Attacks that exploit this kind of access
Cancels an existing pending order. It is categorised as a Destructive tool in the Alpaca MCP Gold Standard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Alpaca MCP Gold Standard MCP server in PolicyLayer and add a rule for cancel_order_tool: 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 Gold Standard. Nothing to install.
cancel_order_tool 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_order_tool 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_order_tool. 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_order_tool is provided by the Alpaca MCP Gold Standard MCP server (joravetz/alpaca-mcp-gold). 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 →