binance_cancel_order
Cancel an open order by orderId or clientOrderId. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY.
This record as markdown: /tools/nirholas-agenti/binance-cancel-order.md
What binance_cancel_order does on Agenti
AI agents call binance_cancel_order to permanently remove resources in Agenti, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why binance_cancel_order is rated Critical
Cancelling an order is an irreversible action that terminates a financial commitment on an exchange. While it doesn't move money directly, it destroys an existing open order which cannot be undone once cancelled. Given the financial context (Binance trading orders) and irreversibility, Destructive is the most appropriate category, with high severity due to potential market and financial impact if misused.
From the tool's definition Cancel an open order by orderId or clientOrderId
Attacks that exploit this kind of access
The rule that runs binance_cancel_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binance_cancel_order, this is the rule to start with:
binance_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 Agenti, apply this rule, and every binance_cancel_order call is checked against it from then on.
Questions about binance_cancel_order
Cancel an open order by orderId or clientOrderId. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY. It is categorised as a Destructive tool in the Agenti MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agenti MCP server in PolicyLayer and add a rule for binance_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 Agenti. Nothing to install.
binance_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 binance_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 binance_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.
binance_cancel_order is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agenti, and thousands of servers like it.
Across the catalogue