Place a new OCO (One-Cancels-the-Other) order through the custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY OCO orders combine a limit order with a stop-loss order. When one executes, the other is automatically canceled. Price Restrictions: - SELL: Limit Price > Last Price > Stop Price -...
AI agents use binance_us_cust_oco_order to commit financial operations through Binance US MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool places live trading orders on a cryptocurrency exchange. Placing an OCO order directly commits financial transactions — buying or selling cryptocurrency assets. Misuse could result in significant financial losses, unintended trades, or market exposure. This clearly falls under the Financial category with critical severity given the potential blast radius of erroneous or malicious order placement.
From the tool's definition Place a new OCO (One-Cancels-the-Other) order through the custodial solution
Documented attack patterns abuse exactly the kind of access binance_us_cust_oco_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance US MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_cust_oco_order:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_cust_oco_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to binance_us_cust_oco_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Place a new OCO (One-Cancels-the-Other) order through the custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY OCO orders combine a limit order with a stop-loss order. When one executes, the other is automatically canceled. Price Restrictions: - SELL: Limit Price > Last Price > Stop Price - BUY: Limit Price < Last Price < Stop Price Quantity: Both legs must have the same quantity (iceberg qty can differ). Note: OCO counts as 2 orders against rate limits. Response includes orderListId, orders array, and orderReports with details. It is categorised as a Financial tool in the Binance US MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_oco_order: 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 US MCP Server. Nothing to install.
binance_us_cust_oco_order 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_cust_oco_order 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_oco_order. 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_oco_order is provided by the Binance US MCP Server MCP server (nirholas/binance-us-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binance US MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Binance US MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.