Get detailed information about a specific OTC (Over-The-Counter) trade order. Use this to check the status and details of a previously placed OTC order. Response includes: - quoteId: Original quote ID used - orderId: Order identifier - orderStatus: SUCCESS, PROCESS, ACCEPT_SUCCESS, or FAIL - from...
AI agents call binance_us_otc_get_order 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 queries existing OTC order data without side effects. It returns status information and historical details about previously placed orders. No financial transactions are initiated, no data is modified, and no external operations are triggered—it is purely informational lookup of financial transaction history.
From the tool's definition Tool description states 'Get detailed information about a specific OTC trade order' and 'Use this to check the status and details of a previously placed OTC order.' The response includes read-only fields (quoteId, orderId, orderStatus, timestamps, amounts,…
Documented attack patterns abuse exactly the kind of access binance_us_otc_get_order 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_otc_get_order:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_otc_get_order": {}
}
}binance_us_otc_get_order 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.
Get detailed information about a specific OTC (Over-The-Counter) trade order. Use this to check the status and details of a previously placed OTC order. Response includes: - quoteId: Original quote ID used - orderId: Order identifier - orderStatus: SUCCESS, PROCESS, ACCEPT_SUCCESS, or FAIL - fromCoin/fromAmount: Sold coin and amount - toCoin/toAmount: Bought coin and amount - ratio/inverseRatio: Exchange rates - createTime: Order creation timestamp. 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_otc_get_order: 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_otc_get_order 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_otc_get_order 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_otc_get_order. 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_otc_get_order 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.