binance_us_new_oco
Place a new OCO (One-Cancels-the-Other) order on Binance.US. OCO orders combine a limit order with a stop-loss order. When one triggers, the other is automatically cancelled. Note: For SELL OCOs, limit price > stop price. For BUY OCOs, limit price < stop price.
This record as markdown: /tools/nirholas-binance-mcp/binance-us-new-oco.md
What binance_us_new_oco does on Binance MCP Server
AI agents use binance_us_new_oco to commit financial operations through Binance MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why binance_us_new_oco is rated Critical
This tool directly places trading orders on a cryptocurrency exchange, committing financial obligations by executing buy or sell transactions with real funds. OCO orders involve two linked orders that trade crypto assets, making this a Financial category tool with critical severity due to potential for significant monetary loss if misused.
From the tool's definition Place a new OCO (One-Cancels-the-Other) order on Binance.US... OCO orders combine a limit order with a stop-loss order.
Attacks that exploit this kind of access
The rule that runs binance_us_new_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_new_oco, this is the rule to start with:
Any call to binance_us_new_oco is blocked until a human approves 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_new_oco call is checked against it from then on.
Questions about binance_us_new_oco
Place a new OCO (One-Cancels-the-Other) order on Binance.US. OCO orders combine a limit order with a stop-loss order. When one triggers, the other is automatically cancelled. Note: For SELL OCOs, limit price > stop price. For BUY OCOs, limit price < stop price. 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 binance_us_new_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_new_oco 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 binance_us_new_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_new_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_new_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