Create a new page in the current Figma document
AI agents use create_page to create or update resources in Claude Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Talk to Figma MCP environment.
Creating a page is a write operation that modifies the Figma document by adding a new resource. It is reversible (pages can be deleted afterward), so it does not qualify as Destructive. The impact is limited to the design workspace with no external side effects or financial implications.
From the tool's definition Tool name 'create_page' and description 'Create a new page in the current Figma document' indicate a create operation that adds a new page to a design document. This is reversible—pages can be deleted.
Documented attack patterns abuse exactly the kind of access create_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 create_page:
{
"version": "1",
"default": "deny",
"tools": {
"create_page": {
"limits": [
{
"counter": "create_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_page stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new page in the current Figma document. It is categorised as a Write tool in the Claude Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for create_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.
create_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.