Fetches all releases from Storyblok space
AI agents call fetch-releases 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 release information from the CMS without creating, modifying, or deleting any data. It is a straightforward query operation that poses minimal security risk if misused by an agent, as the worst outcome would be exposure of release metadata already stored in the system.
From the tool's definition Tool name is 'fetch-releases' and description states it 'Fetches all releases from Storyblok space'. The verb 'fetches' indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Fetches all releases from Storyblok space. 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-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 MCP Storyblok 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 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →