Query all open OCO (One-Cancels-the-Other) orders in Margin account.
AI agents call BinanceMarginGetOpenOco 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 and displays information about existing open OCO orders without performing any side effects such as creating, modifying, canceling, or executing those orders. It is a read-only data retrieval operation. The severity is low because disclosure of order information has minimal direct risk; the blast radius is limited to information exposure rather than financial loss or account compromise.
From the tool's definition The tool name 'BinanceMarginGetOpenOco' and description 'Query all open OCO (One-Cancels-the-Other) orders in Margin account' indicate a retrieval operation using 'Query' and 'Get', with no modification, deletion, or execution of orders—merely viewing…
Documented attack patterns abuse exactly the kind of access BinanceMarginGetOpenOco 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 BinanceMarginGetOpenOco:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceMarginGetOpenOco": {}
}
}BinanceMarginGetOpenOco 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 all open OCO (One-Cancels-the-Other) orders in Margin account. 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 BinanceMarginGetOpenOco: 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.
BinanceMarginGetOpenOco 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 BinanceMarginGetOpenOco 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 BinanceMarginGetOpenOco. 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.
BinanceMarginGetOpenOco 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.