BinanceDeliveryUserTrades
Get COIN-M Futures account trade history for a symbol.
This record as markdown: /tools/nirholas-binance-mcp/binancedeliveryusertrades.md
What BinanceDeliveryUserTrades does on Binance MCP Server
AI agents call BinanceDeliveryUserTrades 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 BinanceDeliveryUserTrades is rated Low
This tool retrieves past transaction history from a user's Binance Futures account. It is a read-only query operation that returns existing data without side effects, modifications, or the ability to execute trades. While the server enables financial operations broadly, this specific tool only accesses historical information, making it a Read classification with low severity.
From the tool's definition Tool name 'BinanceDeliveryUserTrades' and description 'Get COIN-M Futures account trade history for a symbol' indicate retrieval of historical trade data with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs BinanceDeliveryUserTrades 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 BinanceDeliveryUserTrades, this is the rule to start with:
BinanceDeliveryUserTrades 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 BinanceDeliveryUserTrades call is checked against it from then on.
Questions about BinanceDeliveryUserTrades
Get COIN-M Futures account trade history for a symbol. 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 BinanceDeliveryUserTrades: 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.
BinanceDeliveryUserTrades 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 BinanceDeliveryUserTrades 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 BinanceDeliveryUserTrades. 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.
BinanceDeliveryUserTrades 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