fetch_webhooks

What fetch_webhooks does on Storyblok MCP Server

AI agents call fetch_webhooks to retrieve information from Storyblok MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why fetch_webhooks is rated Low

The tool name and verb 'fetch' strongly indicate this retrieves webhook configuration data from Storyblok CMS without modifying it. Even though the description is empty, the naming convention is consistent with Read operations. The low blast radius reflects that viewing webhook configurations poses minimal risk—it returns existing configuration data without triggering actions or modifying state.

From the tool's definition Tool name 'fetch_webhooks' indicates a retrieval operation. The verb 'fetch' is a standard Read operation pattern (fetch, get, retrieve, query). No parameters described that suggest mutation or execution.

The rule that runs fetch_webhooks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Storyblok MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch_webhooks, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_webhooks": {}
  }
}

Questions about fetch_webhooks