binance_us_cancel_oco

Cancel an entire OCO order on Binance.US. Cancelling any individual leg will cancel the entire OCO.

SERVERBinance MCP Server SOURCEnirholas/binance-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-binance-mcp/binance-us-cancel-oco.md

What binance_us_cancel_oco does on Binance MCP Server

AI agents call binance_us_cancel_oco to permanently remove resources in Binance MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why binance_us_cancel_oco is rated Critical

Cancelling an OCO (One-Cancels-the-Other) order is an irreversible action — once cancelled, the order is gone and cannot be restored. This removes active trading orders from the exchange, which could result in missed trades or financial exposure. The description explicitly states cancelling any leg cancels the entire OCO, amplifying the blast radius.

From the tool's definition Cancel an entire OCO order on Binance.US. Cancelling any individual leg will cancel the entire OCO.

Risk signalsBulk/mass operation — affects multiple targets

Questions about binance_us_cancel_oco

What does the binance_us_cancel_oco tool do? +

Cancel an entire OCO order on Binance.US. Cancelling any individual leg will cancel the entire OCO. It is categorised as a Destructive tool in the Binance MCP Server 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 binance_us_cancel_oco? +

Register the Binance MCP Server MCP server in PolicyLayer and add a rule for binance_us_cancel_oco: 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 Binance MCP Server. Nothing to install.

What risk level is binance_us_cancel_oco? +

binance_us_cancel_oco 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 binance_us_cancel_oco? +

Yes. Add a rate_limit block to the binance_us_cancel_oco 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 binance_us_cancel_oco completely? +

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

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

More on Binance MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Binance MCP Server's. Pull the full record:

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.