Low Risk

fetch_presets

fetch_presets

How to control fetch_presets ↓

What fetch_presets does on Storyblok MCP Server

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

The verb 'fetch' and noun 'presets' together indicate this tool retrieves or queries preset configurations from the Storyblok CMS. No side effects, modifications, deletions, or external operations are implied. While the description is empty (lowering confidence slightly), the semantic meaning of 'fetch' as a read operation is sufficiently clear.

From the tool's definition Tool name 'fetch_presets' indicates retrieval of preset configuration data. The name uses 'fetch' which is a standard verb for read-only operations that retrieve existing data without modification.

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

How to control fetch_presets

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

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

fetch_presets 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 fetch_presets

What does the fetch_presets tool do? +

fetch_presets. 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 fetch_presets? +

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

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

Can I rate-limit fetch_presets? +

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

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

fetch_presets is provided by the Storyblok MCP Server MCP server (arjuncodess/storyblok-mcp). 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.

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