Fetch instruments, optionally filtered by ticker or name
AI agents call search_instrument 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 or queries instrument data based on search criteria (ticker or name). It has no side effects—it does not create, modify, delete, or execute any trades or financial transactions. The 'Fetch' operation is a typical Read category action that simply returns market data to support decision-making.
From the tool's definition Tool name is 'search_instrument' and description states 'Fetch instruments, optionally filtered by ticker or name'. The verb 'Fetch' and the filtering parameters indicate data retrieval without modification or execution of operations.
Attacks that exploit this kind of access
Fetch instruments, optionally filtered by ticker or name. 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_instrument: 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_instrument 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_instrument 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_instrument. 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_instrument 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 →