AI agents call fetch_story_schedulings 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.
The 'fetch' verb in the tool name is a standard pattern for retrieval operations that query and return data with no side effects. Even though the description is empty, the naming convention and sibling tools context (which include explicit write/execute/destructive operations like 'copy_stories_between_branches', 'create_branch', 'backup_space') clearly position this as a simple data retrieval function.
From the tool's definition Tool name 'fetch_story_schedulings' with 'fetch' prefix indicates data retrieval operation. The Storyblok CMS context shows this queries scheduling information for stories without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access fetch_story_schedulings 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_story_schedulings:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_story_schedulings": {}
}
}fetch_story_schedulings 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_story_schedulings. 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_story_schedulings: 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_story_schedulings 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_story_schedulings 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_story_schedulings. 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_story_schedulings 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.
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.