AI agents use create-webhook to create or update resources in Mcp Dev — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.
Creating a webhook is a reversible write operation that adds new configuration to the CMS system. While webhooks can potentially trigger external actions when events occur, the tool itself only creates the webhook definition—it does not execute those external calls or delete data.
From the tool's definition Tool name is 'create-webhook' and description states 'Creates a new webhook', which is a data creation operation. Webhooks are configuration objects that trigger external HTTP callbacks on specified events.
Attacks that exploit this kind of access
Creates a new webhook Must contain at least one event from the events listed at /umbraco/management/api/v1/webhook/events endpoint. Cannot mix different event types in the same webhook. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for create-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 Mcp Dev. Nothing to install.
create-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 create-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 create-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.
create-webhook is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). 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 →