Send a new OCO (One-Cancels-the-Other) order on Binance.
AI agents use BinanceOrderOco to commit financial operations through Binance MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool places a live trading order on the Binance exchange. An OCO order involves committing financial obligations by simultaneously placing a limit order and a stop-limit order, directly affecting the user's funds. Misuse could result in unintended trades, significant financial losses, or market exposure. This falls squarely in the Financial category with critical severity due to the direct monetary impact.
From the tool's definition Send a new OCO (One-Cancels-the-Other) order on Binance
Documented attack patterns abuse exactly the kind of access BinanceOrderOco 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 BinanceOrderOco:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceOrderOco": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to BinanceOrderOco is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Send a new OCO (One-Cancels-the-Other) order on Binance. It is categorised as a Financial tool in the Binance MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for BinanceOrderOco: 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.
BinanceOrderOco is a Financial 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 BinanceOrderOco 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 BinanceOrderOco. 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.
BinanceOrderOco is provided by the Binance MCP Server MCP server (termix-official/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 160 Binance MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
160 Binance MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.