binance_us_cust_cancel_oco
Cancel an entire OCO (One-Cancels-the-Other) order list. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY This cancels both legs of the OCO order. Response includes orderListId, orders array, and orderReports with canceled order details.
This record as markdown: /tools/nirholas-binance-mcp/binance-us-cust-cancel-oco.md
What binance_us_cust_cancel_oco does on Binance MCP Server
AI agents call binance_us_cust_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_cust_cancel_oco is rated Critical
This tool irreversibly cancels active financial orders on a cryptocurrency exchange. While not moving funds directly, it destroys pending orders that represent financial commitments/obligations. Combined with the custodial API key requirement (indicating real account access) and the fact that canceled orders cannot be restored, this is Destructive with critical severity.
From the tool's definition 'Cancel an entire OCO (One-Cancels-the-Other) order list' - this irreversibly cancels active trading orders without possibility of restoration. The operation cannot be undone and immediately terminates pending financial orders.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs binance_us_cust_cancel_oco safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binance_us_cust_cancel_oco, this is the rule to start with:
binance_us_cust_cancel_oco 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 Binance MCP Server, apply this rule, and every binance_us_cust_cancel_oco call is checked against it from then on.
Questions about binance_us_cust_cancel_oco
Cancel an entire OCO (One-Cancels-the-Other) order list. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY This cancels both legs of the OCO order. Response includes orderListId, orders array, and orderReports with canceled order details. 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.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_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.
binance_us_cust_cancel_oco 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_us_cust_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.
Set action: deny in the PolicyLayer policy for binance_us_cust_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.
binance_us_cust_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.
Across the catalogue