bn_cancel_order

// WHEN AI AGENTS USE THIS TOOL

AI agents may call bn_cancel_order to permanently remove or destroy resources in Binance. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON BN_CANCEL_ORDER

Without a policy, an AI agent could call bn_cancel_order in a loop, permanently destroying resources in Binance. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

binance.yaml

tools:
  bn_cancel_order:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Binance policy for all 23 tools.

// DETAILS

Tool Name bn_cancel_order

Category Destructive

MCP Server Binance MCP Server

Risk Level Critical

// MORE BINANCE TOOLS

Destructive bn_cancel_all_orders Execute bn_new_order Write bn_close_listen_key Write bn_create_listen_key Write bn_open_orders Read bn_account_info Read bn_aggregate_trades Read bn_all_orders

View all 23 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like bn_cancel_order have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete Agent Passport System — Cryptographic Identity for AI Agents remove_intent_card Agent Passport System — Cryptographic Identity for AI Agents revoke_delegation

// IN CONTEXT OF CRITICAL RISK

bn_cancel_order is one of the critical-risk operations in Binance. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the bn_cancel_order tool do? +

Cancel an active order by orderId or origClientOrderId.. It is categorised as a Destructive tool in the 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_order? +

Add a rule in your Intercept YAML policy under the tools section for bn_cancel_order. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Binance MCP server.

What risk level is bn_cancel_order? +

bn_cancel_order 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_order? +

Yes. Add a rate_limit block to the bn_cancel_order rule in your Intercept 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_order completely? +

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

What MCP server provides bn_cancel_order? +

bn_cancel_order is provided by the Binance MCP server (binance-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.