get_pnl
Get the current profit and loss (PnL) information for the user on Binance.
This record as markdown: /tools/analyticace-binance-mcp-server/get-pnl.md
What get_pnl does on Binance MCP Server
AI agents call get_pnl 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 get_pnl is rated Low
This tool retrieves financial information about the user's portfolio performance (profit/loss) but does not execute trades, transfer funds, or modify any account state. It is a passive data query similar to get_balance and get_orders on the same server. While the data is financially sensitive, the tool itself performs no financial transactions or irreversible actions.
From the tool's definition Tool name 'get_pnl' and description 'Get the current profit and loss (PnL) information' indicate a retrieval operation with no side effects. The verb 'Get' and the informational nature of PnL data confirm this is a read-only query.
Attacks that exploit this kind of access
The rule that runs get_pnl 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 get_pnl, this is the rule to start with:
get_pnl 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 get_pnl call is checked against it from then on.
Questions about get_pnl
Get the current profit and loss (PnL) information for the user on Binance. 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 get_pnl: 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.
get_pnl 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 get_pnl 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 get_pnl. 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.
get_pnl is provided by the Binance MCP Server MCP server (analyticace/binance-mcp-server). 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