AI agents use manage_webhooks to create or update resources in Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kit environment.
While 'delete' appears in the action list, webhook deletion is reversible—a webhook subscription can be recreated. The tool primarily enables creating and modifying webhook subscriptions (Write category). However, improper webhook configuration could redirect Kit events to attacker-controlled endpoints, potentially capturing sensitive email marketing data.
From the tool's definition Tool description explicitly states actions include 'create' and 'delete' webhooks. The 'create' action modifies Kit's webhook configuration by adding new subscriptions.
Attacks that exploit this kind of access
Manage Kit webhooks — list registered webhooks, create new webhook subscriptions for Kit events, or delete webhooks. Actions: list, create, delete. It is categorised as a Write tool in the Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kit MCP server in PolicyLayer and add a rule for manage_webhooks: 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 Kit. Nothing to install.
manage_webhooks 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 manage_webhooks 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 manage_webhooks. 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.
manage_webhooks is provided by the Kit MCP server (@dancumberland/kit-mcp). 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 →