Query a specific OCO order on Binance.US. Either orderListId or origClientOrderId must be provided.
AI agents call binance_us_get_oco to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves order data from Binance.US without side effects. While it relates to financial trading, it does not move money, create new orders, cancel orders, or commit financial obligations—it merely fetches information about an existing order. This qualifies as a Read operation with low severity, as misuse would only expose order information the AI already has access to, not cause financial harm.
From the tool's definition The tool is described as 'Query a specific OCO order on Binance.US' — it retrieves information about an existing order without modifying, deleting, or executing any financial transactions.
Documented attack patterns abuse exactly the kind of access binance_us_get_oco gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_get_oco:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_get_oco": {}
}
}binance_us_get_oco is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query a specific OCO order on Binance.US. Either orderListId or origClientOrderId must be provided. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain 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 BNB Chain MCP. 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 BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.