AI agents call get_trade_history to retrieve information from Binance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical trading data for a cryptocurrency pair without modifying, deleting, or executing any transactions. It is a straightforward data query operation with no capability to affect account state, execute trades, or move funds. The low severity reflects minimal risk even if an AI agent calls it with arbitrary arguments, as the worst outcome would be retrieving unintended historical data.
From the tool's definition Tool name 'get_trade_history' and description 'Get recent trade history for a pair' indicate a query/retrieval operation with no side effects. The verb 'Get' and the use of 'history' confirm read-only access to past transaction data.
Documented attack patterns abuse exactly the kind of access get_trade_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_trade_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_trade_history": {}
}
}get_trade_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get recent trade history for a pair. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for get_trade_history: 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 MCP Server. Nothing to install.
get_trade_history 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_trade_history 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_trade_history. 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_trade_history is provided by the Binance MCP Server MCP server (mixuechu/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binance MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Binance MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.