Fetch all pies
AI agents call fetch_pies to retrieve information from Trading 212 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 portfolio data (pies are Trading 212's portfolio grouping feature) without creating, modifying, deleting, or executing any trades or financial transactions. It has no side effects and poses minimal risk as a standalone read operation. Even in the context of a trading platform with financial implications, a read-only fetch of existing portfolio data is categorized as Read with low severity.
From the tool's definition Tool name 'fetch_pies' and description 'Fetch all pies' indicate a retrieval operation with no modification or execution of trades. The verb 'fetch' is a classic read operation that queries existing data.
Attacks that exploit this kind of access
Fetch all pies. It is categorised as a Read tool in the Trading 212 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trading 212 MCP Server MCP server in PolicyLayer and add a rule for fetch_pies: 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 212 MCP Server. Nothing to install.
fetch_pies 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 fetch_pies 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 fetch_pies. 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.
fetch_pies is provided by the Trading 212 MCP Server MCP server (razeevascx/212mcp). 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 →