Fetch a specific order by ID
AI agents call fetch_order 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 order information by ID without creating, modifying, or deleting any data. While the Trading 212 context involves financial instruments, the tool itself only performs a non-destructive query. The severity is low because reading order data poses minimal risk—an AI misuse would be limited to information disclosure rather than financial transactions or irreversible changes.
From the tool's definition Tool name 'fetch_order' and description 'Fetch a specific order by ID' indicate a retrieval operation with no side effects. The verb 'fetch' is explicitly a read operation that queries existing data.
Attacks that exploit this kind of access
Fetch a specific order by ID. 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_order: 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_order 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_order 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_order. 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_order 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.
fetch_order is one line of Trading 212 MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →