Query a specific order by orderId or origClientOrderId. Returns order status, filled quantity, and execution details.
AI agents call bn_query_order to retrieve information from Node2flow/binance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves order information from the Binance exchange without creating, modifying, deleting, or executing any transactions. It is a read-only operation that queries existing order data. Even in a financial context, querying account/order data is distinct from financial transactions (which would move money or commit obligations).
From the tool's definition Tool description states 'Query a specific order' and 'Returns order status, filled quantity, and execution details.' The verb 'query' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Query a specific order by orderId or origClientOrderId. Returns order status, filled quantity, and execution details. It is categorised as a Read tool in the Node2flow/binance MCP Server, which means it retrieves data without modifying state.
Register the Node2flow/binance MCP server in PolicyLayer and add a rule for bn_query_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 Node2flow/binance. Nothing to install.
bn_query_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 bn_query_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 bn_query_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.
bn_query_order is provided by the Node2flow/binance MCP server (node2flow-th/binance-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →