Finds all stories where a specific component is used, checking direct use and nested use within the story content.
AI agents call get-component-usage 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 retrieves information about component usage across stories without creating, modifying, deleting, or executing any operations. It is purely informational, examining existing data relationships. Despite the presence of destructive tools on the server (bulk-delete-stories, etc.), this specific tool performs read-only queries with no side effects.
From the tool's definition Tool name 'get-component-usage' and description 'Finds all stories where a specific component is used' indicates a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Finds all stories where a specific component is used, checking direct use and nested use within the story content. 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 get-component-usage: 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.
get-component-usage 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 get-component-usage 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 get-component-usage. 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.
get-component-usage 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 →