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.
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.
An AI agent that decides to call binance_us_cust_cancel_oco doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Binance MCP Server is gone — there is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access binance_us_cust_cancel_oco gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_cust_cancel_oco:
{
"version": "1",
"default": "deny",
"hide": [
"binance_us_cust_cancel_oco"
]
}binance_us_cust_cancel_oco disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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.
Deterministic rules across all 734 Binance MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
734 Binance MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.