Low Risk

get_all_instruments

get_all_instruments

How to control get_all_instruments ↓

What get_all_instruments does on Trading212 MCP Server

AI agents call get_all_instruments 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_all_instruments needs a policy

This tool retrieves instrument data (stocks, ETFs, etc.) from the Trading212 brokerage without modifying, executing, or deleting anything. Despite the empty description lowering confidence slightly, the semantic meaning of 'get_all_*' consistently denotes read-only operations across financial APIs. Risk is minimal—an AI agent calling this retrieves publicly available market data.

From the tool's definition Tool name 'get_all_instruments' indicates a retrieval operation. Description is empty, but the naming pattern and server context (sibling tools include 'get_account_info', 'get_portfolio', 'get_pies') establish this as a data-fetching function with no side…

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

How to control get_all_instruments

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

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

get_all_instruments 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_all_instruments

What does the get_all_instruments tool do? +

get_all_instruments. 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_all_instruments? +

Register the Trading212 MCP Server MCP server in PolicyLayer and add a rule for get_all_instruments: 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_all_instruments? +

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

Can I rate-limit get_all_instruments? +

Yes. Add a rate_limit block to the get_all_instruments 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_all_instruments completely? +

Set action: deny in the PolicyLayer policy for get_all_instruments. 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_all_instruments? +

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