Search for available Storyblok API endpoints. Returns operations with their operationId, behavior, and available response fields.\n\nAlways use this first when you don
AI agents call search 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 read-only discovery of API endpoint information. It retrieves and returns data about available operations without side effects, making it a Read category tool. The low severity reflects minimal risk even if misused, as it only exposes API documentation/metadata rather than actual data or operations.
From the tool's definition Tool name is 'search' and description states it 'Search for available Storyblok API endpoints. Returns operations with their operationId, behavior, and available response fields.' This is a metadata/discovery operation that retrieves information about…
Documented attack patterns abuse exactly the kind of access search 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 search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search 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.
Search for available Storyblok API endpoints. Returns operations with their operationId, behavior, and available response fields.\n\nAlways use this first when you don. 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 search: 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.
search 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 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. 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 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.