Adds a new webhook to a specified Storyblok space using the Management API.
AI agents use add_webhook to create or update resources in Storyblok MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storyblok MCP Server environment.
Adding a webhook creates a new persistent configuration that will trigger external HTTP callbacks on content events. While reversible (webhooks can be deleted), this modifies the space's runtime behavior and could redirect sensitive events to attacker-controlled endpoints if misused by a compromised AI agent.
From the tool's definition Tool description states it 'Adds a new webhook to a specified Storyblok space' - this is a creation/modification operation that adds a new configuration resource to the system.
Documented attack patterns abuse exactly the kind of access add_webhook 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 add_webhook:
{
"version": "1",
"default": "deny",
"tools": {
"add_webhook": {
"limits": [
{
"counter": "add_webhook_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_webhook stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Adds a new webhook to a specified Storyblok space using the Management API. It is categorised as a Write tool in the Storyblok MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for add_webhook: 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.
add_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_webhook 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 add_webhook. 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.
add_webhook 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.