Create a section frame in Figma (for organizing related content)
AI agents use create_section to create or update resources in Figma AI Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma AI Bridge environment.
The tool creates new organizational elements (section frames) in a Figma document, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely query information (Read).
From the tool's definition Tool description states 'Create a section frame in Figma' — this creates a new design element that modifies the Figma document structure. The server description confirms 'design creation, editing, and reading operations.'
Documented attack patterns abuse exactly the kind of access create_section gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma AI Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for create_section:
{
"version": "1",
"default": "deny",
"tools": {
"create_section": {
"limits": [
{
"counter": "create_section_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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 section frame in Figma (for organizing related content). It is categorised as a Write tool in the Figma AI Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma AI Bridge MCP server in PolicyLayer and add a rule for 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 AI Bridge. Nothing to install.
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 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 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.
create_section is provided by the Figma AI Bridge MCP server (renfei-design/figma_ai_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma AI 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.
64 Figma AI Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.