Update a webhook
AI agents use figma_update_webhook to create or update resources in Figma MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | — | State of the webhook, including any error state it may be in |
endpoint | string | — | The HTTP endpoint that will receive a POST request when the event triggers |
passcode | string | — | String that will be passed back to your webhook endpoint to verify that it is being called by Figma |
webhook_id | string | — | The ID of the webhook to update |
description | string | — | User provided description or name for the webhook |
Parameters from the server's own tool schema.
This tool modifies webhook configuration reversibly—an updated webhook can be reverted to its previous state by updating it again. It does not delete data (which would be Destructive) or execute arbitrary code (which would be Execute). The impact is confined to webhook settings.
From the tool's definition Tool name 'figma_update_webhook' and description 'Update a webhook' indicate modification of existing webhook configuration. Webhooks are event notification systems that, when updated, can change where and how Figma events are delivered.
Risk signalsAccepts URL/endpoint input (endpoint)
Attacks that exploit this kind of access
Update a webhook. It is categorised as a Write tool in the Figma MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
figma_update_webhook accepts 5 parameters: status, endpoint, passcode, webhook_id, description. The full parameter table on this page comes from the server's own tool schema.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for figma_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 Figma MCP Server. Nothing to install.
figma_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 figma_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 figma_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.
figma_update_webhook is provided by the Figma MCP Server MCP server (thirdstrandstudio/mcp-figma). 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 →