figma_delete_webhook

Delete a webhook

Server Figma MCP Server thirdstrandstudio/mcp-figma
Category Destructive
Risk class Critical
Parameters 10 required

What figma_delete_webhook does on Figma MCP Server

AI agents call figma_delete_webhook to permanently remove resources in Figma MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
webhook_id string The ID of the webhook to delete

Parameters from the server's own tool schema.

Why figma_delete_webhook needs a policy

This tool permanently removes a webhook configuration, which cannot be undone. Webhooks are typically used for automating critical workflows and integrations. Unauthorized deletion could break production automation pipelines, event notifications, or integration dependencies. The irreversibility of the action and potential for disrupting connected systems places this in the Destructive category with high severity.

From the tool's definition Tool name includes 'delete' (figma_delete_webhook) and description states 'Delete a webhook'. Deletion is irreversible.

Questions about figma_delete_webhook

What does the figma_delete_webhook tool do? +

Delete a webhook. It is categorised as a Destructive tool in the Figma MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does figma_delete_webhook accept? +

figma_delete_webhook accepts 1 parameter: webhook_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on figma_delete_webhook? +

Register the Figma MCP Server MCP server in PolicyLayer and add a rule for figma_delete_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.

What risk level is figma_delete_webhook? +

figma_delete_webhook is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit figma_delete_webhook? +

Yes. Add a rate_limit block to the figma_delete_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.

How do I block figma_delete_webhook completely? +

Set action: deny in the PolicyLayer policy for figma_delete_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.

What MCP server provides figma_delete_webhook? +

figma_delete_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.