figma_delete_webhook

// WHEN AI AGENTS USE THIS TOOL

AI agents may call figma_delete_webhook to permanently remove or destroy resources in Figma MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON FIGMA_DELETE_WEBHOOK

Without a policy, an AI agent could call figma_delete_webhook in a loop, permanently destroying resources in Figma MCP Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

thirdstrandstudio-mcp-figma.yaml

tools:
  figma_delete_webhook:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Figma MCP Server policy for all 31 tools.

// DETAILS

Tool Name figma_delete_webhook

Category Destructive

MCP Server Figma MCP Server MCP Server

Risk Level Critical

// MORE FIGMA MCP SERVER TOOLS

Destructive figma_delete_comment Destructive figma_delete_comment_reaction Write figma_post_comment Write figma_post_comment_reaction Write figma_post_webhook Write figma_update_webhook Read figma_get_comment_reactions Read figma_get_comments

View all 31 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like figma_delete_webhook have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete ACR — Agent Composition Records acknowledge_threat AdButler campaign_bulk_delete_catalog_ad_items

// IN CONTEXT OF CRITICAL RISK

figma_delete_webhook is one of the critical-risk operations in Figma MCP Server. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

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.

How do I enforce a policy on figma_delete_webhook? +

Add a rule in your Intercept YAML policy under the tools section for figma_delete_webhook. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Figma MCP Server MCP server.

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 Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.