Searches for a query string within specified fields of story content, with options for content type filtering and deep searching in nested components.
AI agents call search-content 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 content search and retrieval only. It queries existing data without creating, modifying, deleting, or executing operations. The search functionality with filtering options is a typical Read category operation with minimal risk if misused by an AI agent—worst case it exposes data the agent already has access to through the CMS.
From the tool's definition Tool name 'search-content' and description 'Searches for a query string within specified fields of story content' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Searches for a query string within specified fields of story content, with options for content type filtering and deep searching in nested components. 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 search-content: 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.
search-content 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 search-content 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 search-content. 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.
search-content 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 →