Query a specific OCO (One-Cancels-the-Other) order in Margin account by orderListId or listClientOrderId.
AI agents call BinanceMarginGetOco 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 performs a read-only query against a margin trading order system. It retrieves information about an OCO order using identifiers, with no capability to create, modify, cancel, or execute trades. The blast radius if misused by an AI agent is minimal (information disclosure only), making it a low-severity Read operation.
From the tool's definition Tool queries a specific OCO order 'by orderListId or listClientOrderId' — it retrieves existing order data without modification. The verb 'Query' and the readonly nature of order lookup confirm this is a retrieval operation.
Documented attack patterns abuse exactly the kind of access BinanceMarginGetOco 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 BinanceMarginGetOco:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceMarginGetOco": {}
}
}BinanceMarginGetOco 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 (One-Cancels-the-Other) order in Margin account by orderListId or listClientOrderId. 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 BinanceMarginGetOco: 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.
BinanceMarginGetOco 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 BinanceMarginGetOco 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 BinanceMarginGetOco. 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.
BinanceMarginGetOco 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.