create_webhook
AI agents use create_webhook to create or update resources in Klaviyo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Klaviyo MCP Server environment.
This tool creates a new webhook resource, which is a Write operation (creates/modifies data reversibly). It is not Destructive because webhook creation can be undone by deleting the webhook. It is not Execute because it doesn't run arbitrary code—it merely registers a callback endpoint. It is not Financial despite being on a marketing platform, as webhook creation itself doesn't move money.
From the tool's definition Tool name is 'create_webhook' with empty description. In the context of a Klaviyo marketing automation server, webhooks are HTTP endpoints that receive event notifications.
Attacks that exploit this kind of access
create_webhook. It is categorised as a Write tool in the Klaviyo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Klaviyo MCP Server 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 Klaviyo MCP Server. 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 Klaviyo MCP Server MCP server (ivan-rivera-projects/klaviyo-mcp-server-enhanced). 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 →