Register a new outgoing webhook for a project. The webhook will receive HTTP POST requests when subscribed events occur. Events are batched -- delivery happens within a ~3 minute window after the first event. Supported events: translation.created, translation.updated, translation.deleted, transla...
AI agents use create_webhook to create or update resources in Localization — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Localization environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Callback URL -- must accept POST requests with JSON body |
events | array | Yes | Events to subscribe to |
secret | string | — | Optional secret for HMAC-SHA256 signature verification (sent in X-Webhook-Signature header) |
description | string | — | Optional description for this webhook |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
Creating a webhook is a reversible write operation that establishes a new outgoing integration. While it does not directly modify translation data, it creates a persistent configuration that alters system behavior. The tool does not execute arbitrary code immediately, nor does it delete data; it creates a new webhook endpoint subscription.
From the tool's definition Tool description states 'Register a new outgoing webhook' — registers/creates a webhook configuration that persists and modifies the project's notification system.
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (secret)
Attacks that exploit this kind of access
Register a new outgoing webhook for a project. The webhook will receive HTTP POST requests when subscribed events occur. Events are batched -- delivery happens within a ~3 minute window after the first event. Supported events: translation.created, translation.updated, translation.deleted, translation.auto_translated. It is categorised as a Write tool in the Localization MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_webhook accepts 5 parameters: url, events, secret, description, projectSlug. Required: url, events, projectSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Localization 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 Localization. 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 Localization MCP server (localization-mcp-server). 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 →