Get all orders (active, canceled, filled) for a symbol. Supports time range and pagination via orderId.
AI agents call bn_all_orders 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 historical and current order data from the Binance API without any side effects. It does not create, modify, delete, or execute trades—it only queries and returns order information. The supported parameters (time range, pagination via orderId) are all read-only filtering operations.
From the tool's definition Tool name 'bn_all_orders' and description 'Get all orders' indicates data retrieval only. The description specifies querying existing orders (active, canceled, filled) with filtering/pagination but no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get all orders (active, canceled, filled) for a symbol. Supports time range and pagination via orderId. 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_all_orders: 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_all_orders 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_all_orders 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_all_orders. 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_all_orders 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 →