AI agents call fetch_releases 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_releases' tool retrieves or lists existing releases from Storyblok CMS without modifying state. While the description is uninformative, the naming convention aligns clearly with Read category operations (fetch, list, get). No side effects or data mutations are indicated. Severity is low because reading release metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'fetch_releases' indicates retrieval of release data. Description is empty, but the verb 'fetch' combined with the context of a CMS content management server and sibling tools like 'add_story_to_release' and 'backup_space' strongly suggests a…
Documented attack patterns abuse exactly the kind of access fetch_releases 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_releases:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_releases": {}
}
}fetch_releases 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_releases. 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_releases: 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_releases 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_releases 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_releases. 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_releases 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.