AI agents call get_story 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.
This tool performs a data retrieval operation with no capacity to modify, delete, or execute code. It is a simple lookup by ID that returns existing data. The only risk is potential unauthorized access to story content if authentication is compromised, which is a baseline risk for any read operation and qualifies as low severity.
From the tool's definition Tool name is 'get_story' and description states it 'Retrieves a specific story by its ID.' The verb 'retrieves' and the read-only nature of fetching data by identifier indicate no side effects or modifications.
Documented attack patterns abuse exactly the kind of access get_story 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 get_story:
{
"version": "1",
"default": "deny",
"tools": {
"get_story": {}
}
}get_story 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.
Retrieves a specific story by its ID. 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 get_story: 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.
get_story 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 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. 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 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.