bn_cancel_all_orders

Cancel all open orders for a symbol. WARNING: This cancels ALL pending orders at once. Cannot be undone.

Server Node2flow/binance node2flow-th/binance-mcp-community
Category Destructive
Risk class Critical
Parameters 00 required

What bn_cancel_all_orders does on Node2flow/binance

AI agents call bn_cancel_all_orders to permanently remove resources in Node2flow/binance — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why bn_cancel_all_orders needs a policy

This tool cancels all pending orders for a trading symbol, which is an irreversible operation that destroys/removes active financial orders. While it doesn't move money directly, it cancels trading orders that may have significant financial implications for the user's portfolio.

From the tool's definition 'Cancel all open orders for a symbol. WARNING: This cancels ALL pending orders at once. Cannot be undone.' - The description explicitly states the action is irreversible ('Cannot be undone') and affects multiple orders simultaneously.

Questions about bn_cancel_all_orders

What does the bn_cancel_all_orders tool do? +

Cancel all open orders for a symbol. WARNING: This cancels ALL pending orders at once. Cannot be undone. It is categorised as a Destructive tool in the Node2flow/binance MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on bn_cancel_all_orders? +

Register the Node2flow/binance MCP server in PolicyLayer and add a rule for bn_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 Node2flow/binance. Nothing to install.

What risk level is bn_cancel_all_orders? +

bn_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.

Can I rate-limit bn_cancel_all_orders? +

Yes. Add a rate_limit block to the bn_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.

How do I block bn_cancel_all_orders completely? +

Set action: deny in the PolicyLayer policy for bn_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.

What MCP server provides bn_cancel_all_orders? +

bn_cancel_all_orders is provided by the Node2flow/binance MCP server (node2flow-th/binance-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.