Get recent trades for a symbol. Returns up to 1000 most recent trades with price, quantity, and time.
AI agents call bn_recent_trades 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 queries historical trade data from the Binance exchange and returns information only. There are no side effects, state modifications, or financial operations. Public market data retrieval poses minimal security risk even if misused by an AI agent, as it only exposes already-public market information.
From the tool's definition Tool retrieves recent trades data including 'price, quantity, and time' without modifying, creating, or deleting any data. The verb 'Get' and the description 'Returns' indicate a read-only query operation.
Attacks that exploit this kind of access
Get recent trades for a symbol. Returns up to 1000 most recent trades with price, quantity, and time. 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_recent_trades: 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_recent_trades 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_recent_trades 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_recent_trades. 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_recent_trades 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 →