Fetch multiple stories from Storyblok with advanced filtering and pagination.
AI agents call fetch_stories 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.
Fetching stories is a read-only operation that retrieves data without side effects. It does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal - an attacker could potentially access stories they shouldn't see, but cannot alter data or trigger destructive actions. This is categorized as Read with low severity.
From the tool's definition Tool name is 'fetch_stories' and description states it 'Fetch multiple stories from Storyblok' - this is a retrieval operation with 'advanced filtering and pagination' capabilities.
Documented attack patterns abuse exactly the kind of access fetch_stories gives an agent:
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_stories:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_stories": {}
}
}fetch_stories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch multiple stories from Storyblok with advanced filtering and pagination. It is categorised as a Read tool in the Storyblok MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for fetch_stories: 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.
fetch_stories 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_stories 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_stories. 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_stories 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.
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.