cancel_order
Cancel a pending order by ticket number.
This record as markdown: /tools/af7007-mcp-trader/cancel-order.md
What cancel_order does on MCP Trader Server
AI agents call cancel_order to permanently remove resources in MCP Trader Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_order is rated Critical
Cancelling a pending order is an irreversible action: the order is permanently removed from the order book. While it doesn't move money directly, it destroys a financial instrument (a pending trade order) that cannot be undone. This makes it Destructive rather than merely Write.
From the tool's definition Cancel a pending order by ticket number — cancellation of a financial order is irreversible; once cancelled, the pending order is permanently removed and cannot be restored.
Attacks that exploit this kind of access
The rule that runs cancel_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Trader Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_order, this is the rule to start with:
cancel_order 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 MCP Trader Server, apply this rule, and every cancel_order call is checked against it from then on.
Questions about cancel_order
Cancel a pending order by ticket number. It is categorised as a Destructive tool in the MCP Trader Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Trader Server MCP server in PolicyLayer and add a rule for cancel_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 Trader Server. Nothing to install.
cancel_order 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 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. 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 is provided by the MCP Trader Server MCP server (af7007/mcp-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Trader Server, and thousands of servers like it.
Across the catalogue