Delete a page from the current Figma document
AI agents call delete_page to permanently remove resources in Claude Talk to Figma MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a page from a Figma document cannot be undone by the tool itself and destroys all design content, layers, and components contained within that page. This is irreversible data loss and falls squarely into the Destructive category. Severity is high because a single misuse could erase significant design work, though the blast radius is somewhat contained to a single page rather than the entire document.
From the tool's definition Tool name is 'delete_page' and description states 'Delete a page from the current Figma document'. The verb 'delete' is explicit and unambiguous—this operation irreversibly removes a design artifact.
Attacks that exploit this kind of access
Delete a page from the current Figma document. It is categorised as a Destructive tool in the Claude Talk to Figma MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for delete_page: 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 Claude Talk to Figma MCP. Nothing to install.
delete_page 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 delete_page 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 delete_page. 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.
delete_page is provided by the Claude Talk to Figma MCP server (stranyer/claude-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 →