Debugs access to a specific story by trying various fetch parameters.
AI agents call debug-story-access 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 performs read-only operations to diagnose and inspect story access configuration. It attempts various fetch operations to troubleshoot connectivity or permissions, which are intrinsically non-destructive information retrieval actions. The blast radius is minimal as it only returns diagnostic data without modifying any content or system state.
From the tool's definition The tool name 'debug-story-access' and description 'Debugs access to a specific story by trying various fetch parameters' indicate it retrieves information about story access permissions and metadata.
Attacks that exploit this kind of access
Debugs access to a specific story by trying various fetch parameters. 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 debug-story-access: 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.
debug-story-access 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 debug-story-access 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 debug-story-access. 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.
debug-story-access 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 →