Gets a story by its slug using the Content Delivery API
AI agents call get-story-by-slug 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 a story from the Storyblok CMS by its slug identifier. It is a query/fetch operation that reads data without creating, modifying, deleting, or executing any operations. The Content Delivery API is typically read-only. There is minimal risk if misused, as it only exposes existing content that may already be publicly accessible.
From the tool's definition Tool name 'get-story-by-slug' and description 'Gets a story by its slug using the Content Delivery API' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Gets a story by its slug using the Content Delivery API. 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 get-story-by-slug: 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.
get-story-by-slug 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 get-story-by-slug 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 get-story-by-slug. 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.
get-story-by-slug 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 →