BinancePortfolioMarginUmGetUserTrades
Get USDT-M Futures trade history in Portfolio Margin mode.
This record as markdown: /tools/nirholas-binance-mcp/binanceportfoliomarginumgetusertrades.md
What BinancePortfolioMarginUmGetUserTrades does on Binance MCP Server
AI agents call BinancePortfolioMarginUmGetUserTrades 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 BinancePortfolioMarginUmGetUserTrades is rated Low
This tool queries past trade data from a Portfolio Margin USDT-M Futures account. It has no side effects, does not execute trades, modify positions, or transfer funds. It is purely a data retrieval operation that returns existing historical information to the user. Therefore it falls under the Read category with low severity, as misuse would only expose historical information rather than enable harmful actions.
From the tool's definition Tool retrieves 'trade history' with no modification or execution capability. The verb 'Get' and the action of fetching historical records indicates a read-only query operation.
Attacks that exploit this kind of access
The rule that runs BinancePortfolioMarginUmGetUserTrades 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 BinancePortfolioMarginUmGetUserTrades, this is the rule to start with:
BinancePortfolioMarginUmGetUserTrades 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 BinancePortfolioMarginUmGetUserTrades call is checked against it from then on.
Questions about BinancePortfolioMarginUmGetUserTrades
Get USDT-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 BinancePortfolioMarginUmGetUserTrades: 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.
BinancePortfolioMarginUmGetUserTrades 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 BinancePortfolioMarginUmGetUserTrades 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 BinancePortfolioMarginUmGetUserTrades. 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.
BinancePortfolioMarginUmGetUserTrades 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