Create a labeled section. Sections work in BOTH Figma design files and FigJam — use them to group flowcharts, diagrams, or design areas. Supports dev status (READY_FOR_DEV/COMPLETED) for handoff.
AI agents use figma_create_section 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.
This tool creates a new section in a Figma document, which is a write operation that adds content to a design file. Sections are organizational constructs that group design elements and can be deleted or modified later, making this reversible. The operation has limited blast radius — it cannot delete data, execute arbitrary code, or cause financial harm.
From the tool's definition Tool name 'figma_create_section' and description explicitly states 'Create a labeled section' — a reversible creation operation that modifies a Figma document by adding a new organizational element.
Documented attack patterns abuse exactly the kind of access figma_create_section 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_section:
{
"version": "1",
"default": "deny",
"tools": {
"figma_create_section": {
"limits": [
{
"counter": "figma_create_section_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}figma_create_section 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 labeled section. Sections work in BOTH Figma design files and FigJam — use them to group flowcharts, diagrams, or design areas. Supports dev status (READY_FOR_DEV/COMPLETED) for handoff. 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_section: 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_section 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_section 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_section. 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_section 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.