Create a new page in the document. Figma Design only — not available in FigJam. Calling this in a FigJam file returns a FIGMA_DESIGN_ONLY error. FigJam files have pages but the plugin API does not expose figma.createPage(); pages must be created via the FigJam UI.
AI agents use figma_create_page to create or update resources in Figma MCP Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma MCP Bridge environment.
Creating a new page is a Write operation: it adds new data (a page) to the document that can be deleted or undone. It is not destructive because pages can be removed without permanent loss, and the blast radius is minimal—a misused tool would add an unwanted page, which is easily correctable. No code execution, data deletion, or financial impact is involved.
From the tool's definition Tool description states 'Create a new page in the document' — a reversible creation operation that modifies the Figma document structure.
Documented attack patterns abuse exactly the kind of access figma_create_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for figma_create_page:
{
"version": "1",
"default": "deny",
"tools": {
"figma_create_page": {
"limits": [
{
"counter": "figma_create_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} figma_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 document. Figma Design only — not available in FigJam. Calling this in a FigJam file returns a FIGMA_DESIGN_ONLY error. FigJam files have pages but the plugin API does not expose figma.createPage(); pages must be created via the FigJam UI. It is categorised as a Write tool in the Figma MCP Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma MCP Bridge MCP server in PolicyLayer and add a rule for figma_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 Figma MCP Bridge. Nothing to install.
figma_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 figma_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 figma_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.
figma_create_page is provided by the Figma MCP Bridge MCP server (magic-spells/figma-mcp-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma MCP Bridge, 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.
88 Figma MCP Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.