binance_us_all_oco_orders

Get all OCO orders (history) on Binance.US. Returns up to 1000 orders.

SERVERBinance MCP Server SOURCEnirholas/binance-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-binance-mcp/binance-us-all-oco-orders.md

WHAT IT DOES

What binance_us_all_oco_orders does on Binance MCP Server

AI agents call binance_us_all_oco_orders to retrieve information from Binance MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why binance_us_all_oco_orders is rated Low

This tool retrieves and queries existing OCO (One-Cancels-Other) order history from Binance.US without any capability to modify, delete, or execute financial transactions. It has no side effects on account state or assets. The blast radius of misuse is limited to information disclosure of the user's past orders, which is a low severity risk. The tool is purely informational.

From the tool's definition The tool description states 'Get all OCO orders (history)' which explicitly retrieves historical order data without modifying or executing any actions. The verb 'Get' and the mention of 'history' indicate a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs binance_us_all_oco_orders 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_all_oco_orders, this is the rule to start with:

binance_us_all_oco_orders Allowed

binance_us_all_oco_orders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "binance_us_all_oco_orders": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every binance_us_all_oco_orders call is checked against it from then on.

FAQ

Questions about binance_us_all_oco_orders

What does the binance_us_all_oco_orders tool do? +

Get all OCO orders (history) on Binance.US. Returns up to 1000 orders. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on binance_us_all_oco_orders? +

Register the Binance MCP Server MCP server in PolicyLayer and add a rule for binance_us_all_oco_orders: 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.

What risk level is binance_us_all_oco_orders? +

binance_us_all_oco_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit binance_us_all_oco_orders? +

Yes. Add a rate_limit block to the binance_us_all_oco_orders 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.

How do I block binance_us_all_oco_orders completely? +

Set action: deny in the PolicyLayer policy for binance_us_all_oco_orders. 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.

What MCP server provides binance_us_all_oco_orders? +

binance_us_all_oco_orders 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.

KEEP EXPLORING

More on Binance MCP Server, and thousands of servers like it.

This server

All 734 Binance MCP Server tools →

Across the catalogue

shopify_get_orders on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →