Execute a read-only Storyblok API operation. Use for operations with behavior:
AI agents call execute_readonly 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 tool is explicitly labeled 'readonly' and described as executing read-only API operations, indicating it only retrieves or queries data without side effects. The description is incomplete but the 'readonly' qualifier strongly implies no mutation occurs. Severity is low since misuse only exposes data without modifying it.
From the tool's definition Tool name 'execute_readonly' and description 'Execute a read-only Storyblok API operation. Use for operations with behavior:'
Documented attack patterns abuse exactly the kind of access execute_readonly 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 execute_readonly:
{
"version": "1",
"default": "deny",
"tools": {
"execute_readonly": {}
}
}execute_readonly 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.
Execute a read-only Storyblok API operation. Use for operations with behavior:. 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 execute_readonly: 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.
execute_readonly 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 execute_readonly 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 execute_readonly. 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.
execute_readonly is provided by the Storyblok MCP Server MCP server (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.
5 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.