The API retrieves your token conversion trade history within a specified time range, with support for pagination using the limit parameter (up to 1000 records).
AI agents call BinanceGetConvertTradeHistory 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 queries past conversion trades and returns historical data with no side effects or data modification. It falls squarely in the Read category. However, severity is raised from 'low' to 'medium' because access to detailed trading history and account activity could enable social engineering, market manipulation insights, or competitive intelligence if misused by an unauthorized agent, despite the lack of…
From the tool's definition The tool 'retrieves your token conversion trade history' with 'support for pagination'. The verb 'retrieves' and the retrieval of historical data without modification indicate a read operation.
Documented attack patterns abuse exactly the kind of access BinanceGetConvertTradeHistory 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 BinanceGetConvertTradeHistory:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceGetConvertTradeHistory": {}
}
}BinanceGetConvertTradeHistory 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.
The API retrieves your token conversion trade history within a specified time range, with support for pagination using the limit parameter (up to 1000 records). 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 BinanceGetConvertTradeHistory: 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.
BinanceGetConvertTradeHistory 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 BinanceGetConvertTradeHistory 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 BinanceGetConvertTradeHistory. 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.
BinanceGetConvertTradeHistory is provided by the Binance MCP Server MCP server (termix-official/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 160 Binance MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
160 Binance MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.