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 design document destroys all content within that page and cannot be undone by the tool itself. This is irreversible data loss, placing it firmly in the Destructive category. Severity is high because a single misused call could destroy hours of design work, though the blast radius is limited to one page rather than the entire document or account.
From the tool's definition Tool name is 'delete_page' with description 'Delete a page from the current Figma document'. The verb 'delete' is unambiguous—this operation irreversibly removes a page and its contents.
Documented attack patterns abuse exactly the kind of access delete_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Talk to Figma MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_page:
{
"version": "1",
"default": "deny",
"hide": [
"delete_page"
]
} delete_page disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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 (arinspunk/claude-talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Talk to Figma MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Claude Talk to Figma MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.