Low Risk

retrieve_field_plugin

Retrieves a single field plugin by its ID in the specified context.

How to control retrieve_field_plugin ↓

What retrieve_field_plugin does on Storyblok MCP Server

AI agents call retrieve_field_plugin to retrieve information from Storyblok 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 retrieve_field_plugin needs a policy

This tool performs a read-only query to fetch a field plugin configuration by identifier. It does not create, modify, delete, or execute any operations—it only retrieves existing data from the Storyblok CMS. The blast radius of misuse is minimal, as an AI agent could at most expose plugin metadata already stored in the system.

From the tool's definition Tool name 'retrieve_field_plugin' and description 'Retrieves a single field plugin by its ID' indicate a data retrieval operation with no modification or side effects.

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

How to control retrieve_field_plugin

PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for retrieve_field_plugin:

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

retrieve_field_plugin 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 Storyblok 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 retrieve_field_plugin

What does the retrieve_field_plugin tool do? +

Retrieves a single field plugin by its ID in the specified context. It is categorised as a Read tool in the Storyblok MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieve_field_plugin? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for retrieve_field_plugin: 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 Storyblok MCP Server. Nothing to install.

What risk level is retrieve_field_plugin? +

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

Can I rate-limit retrieve_field_plugin? +

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

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

retrieve_field_plugin is provided by the Storyblok MCP Server MCP server (kiran1689/storyblok-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Storyblok MCP Server tool call.

Start from Storyblok 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.

159 Storyblok 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.