unrealized_gains
AI agents call unrealized_gains to retrieve information from Trading MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calculated financial data (unrealized gains on open positions) without modifying portfolio state, executing trades, or committing financial transactions. It is a read-only query operation similar to the other non-trading tools on this server. Confidence slightly reduced due to empty description, but the naming pattern and sibling context strongly indicate passive data retrieval.
From the tool's definition Tool name 'unrealized_gains' and server context indicate querying portfolio performance metrics. No description provided, but sibling tools like 'portfolio', 'pnl', 'realized_gains', and 'trade_history' establish this as a data retrieval server.
Attacks that exploit this kind of access
unrealized_gains. It is categorised as a Read tool in the Trading MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trading MCP Server MCP server in PolicyLayer and add a rule for unrealized_gains: 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 Trading MCP Server. Nothing to install.
unrealized_gains 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 unrealized_gains 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 unrealized_gains. 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.
unrealized_gains is provided by the Trading MCP Server MCP server (vaishnavik23/trading-mcp-server). 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 →