Update an existing webhook configuration. You can change the URL, events, enabled status, description, or secret.
AI agents use update_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 | — | New callback URL |
events | array | — | New event subscriptions |
secret | string | — | New HMAC secret |
enabled | boolean | — | Enable or disable the webhook |
webhookId | string | Yes | Webhook ID |
description | string | — | New description |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
The tool performs configuration updates (change URL, events, enabled status, description, secret) which are write operations that alter system state. These changes are reversible, so it does not qualify as Destructive.
From the tool's definition Tool name 'update_webhook' and description state it modifies webhook configuration by changing URL, events, enabled status, description, or secret. This is a reversible modification operation.
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (secret)
Attacks that exploit this kind of access
Update an existing webhook configuration. You can change the URL, events, enabled status, description, or secret. 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.
update_webhook accepts 7 parameters: url, events, secret, enabled, webhookId, description, projectSlug. Required: webhookId, 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 update_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.
update_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 update_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 update_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.
update_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 →