Duplicate a pie with new name/icon
AI agents use duplicate_pie to create or update resources in Trading 212 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trading 212 MCP Server environment.
Duplicating a pie creates a new financial portfolio structure but does not move money, execute trades, or irreversibly delete data. It is a Write operation. However, in a financial context, misuse could lead to unintended portfolio structures being created, warranting medium severity.
From the tool's definition Duplicate a pie with new name/icon — creates a new copy of an existing pie (a portfolio allocation structure), which is a reversible write operation
Attacks that exploit this kind of access
Duplicate a pie with new name/icon. It is categorised as a Write tool in the Trading 212 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trading 212 MCP Server MCP server in PolicyLayer and add a rule for duplicate_pie: 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.
duplicate_pie is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the duplicate_pie 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 duplicate_pie. 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.
duplicate_pie 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 →