Get exchange information including trading rules, symbol list, filters (PRICE_FILTER, LOT_SIZE, MIN_NOTIONAL), and rate limits. Optionally filter by symbol.
AI agents call bn_exchange_info 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.
bn_exchange_info retrieves public exchange configuration data. It performs no writes, executions, deletions, or financial operations. Even though it's part of a Binance trading platform, this specific tool only queries and returns informational metadata. The optional symbol filter is a query parameter, not a modification. Severity is low because misuse poses no risk to accounts, funds, or data integrity.
From the tool's definition Tool description: 'Get exchange information including trading rules, symbol list, filters... and rate limits.' The verb 'Get' and the read-only nature of querying static exchange metadata (rules, symbols, filters, rate limits) with no modifications or side…
Attacks that exploit this kind of access
Get exchange information including trading rules, symbol list, filters (PRICE_FILTER, LOT_SIZE, MIN_NOTIONAL), and rate limits. Optionally filter by symbol. 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_exchange_info: 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_exchange_info 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_exchange_info 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_exchange_info. 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_exchange_info 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 →