Low Risk

get_instrument_list

get_instrument_list

How to control get_instrument_list ↓

What get_instrument_list does on Trading212 MCP Server

AI agents call get_instrument_list 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.

Low Risk

Why get_instrument_list needs a policy

The tool retrieves or lists available instruments (stocks, ETFs, etc.) without modifying state, executing code, or committing financial transactions. The function name's 'get' verb and the pattern of sibling read operations strongly suggest this is a query tool for browsing investment options.

From the tool's definition Tool name 'get_instrument_list' indicates a retrieval operation. Description is empty, but sibling tools like 'get_all_instruments', 'get_instrument', and 'search_instruments' on this Trading212 brokerage server are all read-only query operations.

Documented attack patterns abuse exactly the kind of access get_instrument_list gives an agent:

How to control get_instrument_list

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_instrument_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_instrument_list": {}
  }
}

get_instrument_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Trading212 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_instrument_list

What does the get_instrument_list tool do? +

get_instrument_list. It is categorised as a Read tool in the Trading212 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_instrument_list? +

Register the Trading212 MCP Server MCP server in PolicyLayer and add a rule for get_instrument_list: 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.

What risk level is get_instrument_list? +

get_instrument_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_instrument_list? +

Yes. Add a rate_limit block to the get_instrument_list 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.

How do I block get_instrument_list completely? +

Set action: deny in the PolicyLayer policy for get_instrument_list. 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.

What MCP server provides get_instrument_list? +

get_instrument_list 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.

Enforce policy on every Trading212 MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.