AI agents call get_pie_details to retrieve information from Trading212 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to fetch details about an investment pie (a portfolio basket feature in Trading212). The 'get_' prefix indicates a query operation that retrieves existing data with no side effects. Even though the description is empty, the naming pattern and context of peer tools on the server (get_account_info, get_portfolio, get_pies) confirm this is a Read operation.
From the tool's definition Tool name 'get_pie_details' follows a 'get_*' pattern, which retrieves data without modification. The sibling tool 'get_pies' and similar read-only tools (get_account_info, get_portfolio, get_instrument) establish this server's naming convention for retrieval…
Documented attack patterns abuse exactly the kind of access get_pie_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trading212 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pie_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_pie_details": {}
}
}get_pie_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_pie_details. It is categorised as a Read tool in the Trading212 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trading212 MCP Server MCP server in PolicyLayer and add a rule for get_pie_details: 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 Trading212 MCP Server. Nothing to install.
get_pie_details 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_pie_details 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_pie_details. 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_pie_details is provided by the Trading212 MCP Server MCP server (lukeplausin/mcp-server-trading212). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Trading212 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Trading212 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.