Get all positions (auto-derived from transaction history), optionally filtered by status
AI agents call list_positions 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 lists existing investment positions derived from transaction history. It performs no data modification, deletion, code execution, or financial transactions. The operation is purely informational and has no side effects beyond returning data to the caller.
From the tool's definition Tool name 'list_positions' and description 'Get all positions' indicate a retrieval operation with no modifications or side effects. The optional filtering by status is a read-only query parameter.
Attacks that exploit this kind of access
Get all positions (auto-derived from transaction history), optionally filtered by status. 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 list_positions: 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.
list_positions 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 list_positions 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 list_positions. 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.
list_positions 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 →