Fetch exchanges, optionally filtered by name or ID
AI agents call search_exchange 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 exchange data without side effects. It does not create, modify, delete, or execute any operations. While the server context involves financial trading, this specific tool merely queries and returns exchange information, making it a straightforward Read operation with low severity risk.
From the tool's definition Tool description states 'Fetch exchanges' with optional filtering by name or ID. The verb 'fetch' and the absence of any modification, creation, deletion, or execution language clearly indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Fetch exchanges, optionally filtered by name or 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 search_exchange: 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.
search_exchange 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 search_exchange 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 search_exchange. 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.
search_exchange 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 →