BinancePortfolioMarginCmGetUserTrades
Get COIN-M Futures trade history in Portfolio Margin mode.
This record as markdown: /tools/nirholas-binance-mcp/binanceportfoliomargincmgetusertrades.md
What BinancePortfolioMarginCmGetUserTrades does on Binance MCP Server
AI agents call BinancePortfolioMarginCmGetUserTrades 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 BinancePortfolioMarginCmGetUserTrades is rated Low
This tool retrieves past trade data from the user's account without creating, modifying, deleting, or executing any financial transactions. It is purely informational and has no side effects beyond exposing existing historical records. While this is a financial system, the tool itself does not move money or commit financial obligations—it only reads data.
From the tool's definition The tool description explicitly states it 'Get[s]' trade history, which is a retrieval operation with no modification or execution of orders. The verb 'Get' indicates read-only access to historical data.
Attacks that exploit this kind of access
The rule that runs BinancePortfolioMarginCmGetUserTrades 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 BinancePortfolioMarginCmGetUserTrades, this is the rule to start with:
BinancePortfolioMarginCmGetUserTrades 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 BinancePortfolioMarginCmGetUserTrades call is checked against it from then on.
Questions about BinancePortfolioMarginCmGetUserTrades
Get COIN-M Futures trade history in Portfolio Margin mode. 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 BinancePortfolioMarginCmGetUserTrades: 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.
BinancePortfolioMarginCmGetUserTrades 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 BinancePortfolioMarginCmGetUserTrades 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 BinancePortfolioMarginCmGetUserTrades. 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.
BinancePortfolioMarginCmGetUserTrades 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