BinanceGetPayTradeHistory
Retrieve Binance Pay trade history using GET to fetch transaction records such as C2C transfers, merchant payments, crypto box activity, refunds, payouts, and remittance details.
This record as markdown: /tools/nirholas-binance-mcp/binancegetpaytradehistory.md
What BinanceGetPayTradeHistory does on Binance MCP Server
AI agents call BinanceGetPayTradeHistory to retrieve information from Binance MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why BinanceGetPayTradeHistory is rated Low
While the tool accesses sensitive financial transaction history (which justifies medium severity due to potential information disclosure and account privacy risks), it performs no write, execution, destruction, or financial transaction operations. The GET method and 'fetch' language confirm read-only semantics.
From the tool's definition Tool description explicitly states 'Retrieve Binance Pay trade history using GET to fetch transaction records' — this is a read-only operation that retrieves historical data without modifying or executing transactions.
Attacks that exploit this kind of access
The rule that runs BinanceGetPayTradeHistory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For BinanceGetPayTradeHistory, this is the rule to start with:
BinanceGetPayTradeHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every BinanceGetPayTradeHistory call is checked against it from then on.
Questions about BinanceGetPayTradeHistory
Retrieve Binance Pay trade history using GET to fetch transaction records such as C2C transfers, merchant payments, crypto box activity, refunds, payouts, and remittance details. 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 BinanceGetPayTradeHistory: 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.
BinanceGetPayTradeHistory 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 BinanceGetPayTradeHistory 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 BinanceGetPayTradeHistory. 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.
BinanceGetPayTradeHistory is provided by the Binance MCP Server MCP server (nirholas/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue