Cancel an entire OCO (One-Cancels-the-Other) order in Margin account. Both legs will be cancelled.
AI agents call BinanceMarginCancelOco to permanently remove resources in BNB Chain MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling both legs of an OCO order in a margin account is an irreversible financial operation — once cancelled, those orders cannot be reinstated. While it involves financial trading infrastructure, the primary action is irreversible cancellation of existing orders, making Destructive the most appropriate category.
From the tool's definition Cancel an entire OCO (One-Cancels-the-Other) order in Margin account. Both legs will be cancelled.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access BinanceMarginCancelOco gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceMarginCancelOco:
{
"version": "1",
"default": "deny",
"hide": [
"BinanceMarginCancelOco"
]
}BinanceMarginCancelOco 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 in Margin account. Both legs will be cancelled. It is categorised as a Destructive tool in the BNB Chain MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BNB Chain MCP server in PolicyLayer and add a rule for BinanceMarginCancelOco: 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 BNB Chain MCP. Nothing to install.
BinanceMarginCancelOco 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 BinanceMarginCancelOco 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 BinanceMarginCancelOco. 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.
BinanceMarginCancelOco is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.