Delete a comment from a Figma file
AI agents call figma_delete_comment 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
fileKey | string | — | The file key to use for the operation |
commentId | string | — | The ID of the comment to delete |
Parameters from the server's own tool schema.
The tool permanently removes a comment, which cannot be undone. Deletion of data is classified as Destructive. While the blast radius is somewhat limited (affecting only a single comment rather than entire files), unauthorized deletion of comments could disrupt collaboration, remove important feedback, or alter the audit trail of design decisions in a Figma project.
From the tool's definition Tool name 'figma_delete_comment' and description 'Delete a comment from a Figma file' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete a comment from a Figma file. 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.
figma_delete_comment accepts 2 parameters: fileKey, commentId. 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_delete_comment: 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_delete_comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the figma_delete_comment 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_delete_comment. 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_delete_comment 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 →