Fetches components from Storyblok space, with optional filtering and response shaping.
AI agents call fetch-components to retrieve information from MCP Storyblok Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves component data from Storyblok CMS without creating, modifying, or deleting any resources. It is a pure read operation with minimal security risk—an AI agent using this tool cannot cause irreversible harm or modify state. Low severity is appropriate for a read-only data query.
From the tool's definition Tool name 'fetch-components' and description 'Fetches components from Storyblok space' indicates data retrieval with no modification. The phrase 'optional filtering and response shaping' confirms read-only querying without side effects.
Attacks that exploit this kind of access
Fetches components from Storyblok space, with optional filtering and response shaping. It is categorised as a Read tool in the MCP Storyblok Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Storyblok Server MCP server in PolicyLayer and add a rule for fetch-components: 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 MCP Storyblok Server. Nothing to install.
fetch-components 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 fetch-components 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 fetch-components. 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.
fetch-components is provided by the MCP Storyblok Server MCP server (zerdos/mcp-storyblok-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
fetch-components is one line of MCP Storyblok Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →