Cancel an existing order
AI agents call cancel_order to permanently remove resources in Zerodha Trading Bot - MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Order cancellation is irreversible; once cancelled, the order is permanently removed and cannot be restored to its prior pending state. While not a direct financial transaction like place_order, it irrevocably modifies the state of a live trading order. This qualifies as Destructive rather than Write (which is reversible) or Execute (which is contingent).
From the tool's definition Tool cancels an existing order, which is an irreversible action that removes a pending order from the market. The description states 'Cancel an existing order' - cancel is a destructive operation that cannot be undone once executed.
Attacks that exploit this kind of access
Cancel an existing order. It is categorised as a Destructive tool in the Zerodha Trading Bot - MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zerodha Trading Bot - MCP 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 Zerodha Trading Bot - MCP 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 Zerodha Trading Bot - MCP Server MCP server (ssonthal/zerodhatradingbot-mcpserver). 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 →