Retrieves all comments from a specific discussion via the Storyblok Management API.
AI agents call retrieve_multiple_comments 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 read-only query operation to fetch existing comments. It retrieves data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could only over-retrieve or access comments it shouldn't, but cannot alter content or trigger external operations.
From the tool's definition Tool name 'retrieve_multiple_comments' and description 'Retrieves all comments from a specific discussion' indicate a data retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access retrieve_multiple_comments 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 retrieve_multiple_comments:
{
"version": "1",
"default": "deny",
"tools": {
"retrieve_multiple_comments": {}
}
}retrieve_multiple_comments 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 all comments from a specific discussion via the Storyblok Management API. 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 retrieve_multiple_comments: 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.
retrieve_multiple_comments 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 retrieve_multiple_comments 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 retrieve_multiple_comments. 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.
retrieve_multiple_comments 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.