Create a webhook
AI agents use figma_post_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 |
team_id | string | — | Team id to receive updates about |
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 |
event_type | string | — | An enum representing the possible events that a webhook can subscribe to |
description | string | — | User provided description or name for the webhook |
Parameters from the server's own tool schema.
Creating a webhook is a write operation that establishes a new integration configuration. While webhooks can trigger external events, the tool itself only creates/registers the webhook (reversible via deletion). The severity is medium because a misconfigured webhook could potentially expose data or trigger unintended automations, but the operation itself is not destructive or financially consequential.
From the tool's definition Tool name 'figma_post_webhook' with description 'Create a webhook' indicates creation of a new webhook resource, which is a reversible write operation.
Risk signalsAccepts URL/endpoint input (endpoint)
Attacks that exploit this kind of access
Create 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_post_webhook accepts 6 parameters: status, team_id, endpoint, passcode, event_type, 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_post_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_post_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_post_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_post_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_post_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 →