Get portfolio statistics and summary, including unrealized gains using live prices
AI agents call get_portfolio_stats to retrieve information from My Portfolio 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 and summarizes portfolio data (statistics, unrealized gains) with no capability to create, modify, delete, or execute code. It is a pure read operation with minimal security risk—the worst case is information disclosure of the user's own portfolio data.
From the tool's definition Tool description states 'Get portfolio statistics and summary' — a retrieval operation that queries and returns data about the portfolio without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get portfolio statistics and summary, including unrealized gains using live prices. It is categorised as a Read tool in the My Portfolio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the My Portfolio MCP Server MCP server in PolicyLayer and add a rule for get_portfolio_stats: 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 My Portfolio MCP Server. Nothing to install.
get_portfolio_stats 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_portfolio_stats 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_portfolio_stats. 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_portfolio_stats is provided by the My Portfolio MCP Server MCP server (udaybhasker-ub/my-portfolio-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 →