get_historical_trades
AI agents call get_historical_trades to retrieve information from Binance Cryptocurrency MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical trade data from Binance—a read-only query with no ability to modify, execute, delete, or commit financial transactions. The blast radius of misuse is minimal: an agent could only retrieve historical trading information already public on the exchange.
From the tool's definition Tool name 'get_historical_trades' indicates data retrieval. All sibling tools (get_24hr_ticker, get_aggregate_trades, get_avg_price, get_book_ticker, get_klines, get_order_book, get_price, get_recent_trades, get_rolling_window_ticker, get_trading_day_ticker)…
Attacks that exploit this kind of access
get_historical_trades. It is categorised as a Read tool in the Binance Cryptocurrency MCP MCP Server, which means it retrieves data without modifying state.
Register the Binance Cryptocurrency MCP server in PolicyLayer and add a rule for get_historical_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 Binance Cryptocurrency MCP. Nothing to install.
get_historical_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 get_historical_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 get_historical_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.
get_historical_trades is provided by the Binance Cryptocurrency MCP server (jianchundev/binance-mcp). 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 →