AI agents use group_nodes 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.
Grouping nodes is a reversible modification operation that changes document structure but does not delete data or trigger external operations. It qualifies as Write rather than Execute because it performs a specific, bounded design operation (grouping) rather than executing arbitrary code.
From the tool's definition Tool groups multiple nodes together in Figma, which creates a new container object and modifies the document structure.
Documented attack patterns abuse exactly the kind of access group_nodes 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 group_nodes:
{
"version": "1",
"default": "deny",
"tools": {
"group_nodes": {
"limits": [
{
"counter": "group_nodes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}group_nodes 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.
Group multiple nodes together in Figma. 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 group_nodes: 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.
group_nodes 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 group_nodes 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 group_nodes. 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.
group_nodes 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.