AI agents call get_wallet_pnl to retrieve information from Zerion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial performance metrics for a wallet (unrealized PnL, realized PnL, net invested). It does not create, modify, delete, or execute transactions. However, it accesses sensitive financial data that could reveal portfolio composition, gains/losses, and net investment amounts. If an agent queries this for wallets without proper authorization, it could leak sensitive financial information.
From the tool's definition Tool name contains 'get_' and description states it retrieves 'Profit and Loss (PnL) for a wallet' with no modification capabilities mentioned. The verb 'Get' and the passive construction 'Uses FIFO accounting' indicate pure data retrieval.
Attacks that exploit this kind of access
Get Profit and Loss (PnL) for a wallet: unrealized PnL, realized PnL, net invested. Uses FIFO accounting. It is categorised as a Read tool in the Zerion MCP Server, which means it retrieves data without modifying state.
Register the Zerion MCP server in PolicyLayer and add a rule for get_wallet_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 Zerion. Nothing to install.
get_wallet_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_wallet_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_wallet_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_wallet_pnl is provided by the Zerion MCP server (rockyale/zerion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →