binance_us_get_oco
Query a specific OCO order on Binance.US. Either orderListId or origClientOrderId must be provided.
This record as markdown: /tools/nirholas-binance-us-mcp/binance-us-get-oco.md
What binance_us_get_oco does on Binance US MCP Server
AI agents call binance_us_get_oco to retrieve information from Binance US MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why binance_us_get_oco is rated Low
This tool retrieves information about an existing OCO (One-Cancels-Other) order without modifying, canceling, or executing any trades. It is a passive query operation that returns account/order data. While it operates on a financial exchange, the tool itself does not move money, execute trades, or commit financial obligations—it only reads order information.
From the tool's definition Tool name 'get_oco' and description 'Query a specific OCO order' indicate data retrieval with no side effects. The verb 'query' and the read-only nature of fetching order status information confirm this is a Read operation.
Attacks that exploit this kind of access
The rule that runs binance_us_get_oco safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance US 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_get_oco, this is the rule to start with:
binance_us_get_oco is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance US MCP Server, apply this rule, and every binance_us_get_oco call is checked against it from then on.
Questions about binance_us_get_oco
Query a specific OCO order on Binance.US. Either orderListId or origClientOrderId must be provided. It is categorised as a Read tool in the Binance US MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_get_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 US MCP Server. Nothing to install.
binance_us_get_oco is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the binance_us_get_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_get_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_get_oco 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.
More on Binance US MCP Server, and thousands of servers like it.
This server
Across the catalogue