Create multiple presentation slides in Figma in a single batch call. Much faster than creating slides one at a time. Each slide can be of type: title, content, visual, statement, columns, comparison, or numbered.
AI agents use batch_slides 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.
This tool creates new presentation slides reversibly within Figma. While it modifies the design document, the changes are not destructive—slides can be deleted or edited afterwards. The batch nature increases the blast radius compared to single operations (potential for creating many unwanted slides), but it remains a Write operation rather than Execute or Destructive.
From the tool's definition Tool description states 'Create multiple presentation slides in Figma' and 'Much faster than creating slides one at a time.' The verb 'create' combined with the batch operation on design elements indicates this tool creates and modifies data within Figma.
Documented attack patterns abuse exactly the kind of access batch_slides 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 batch_slides:
{
"version": "1",
"default": "deny",
"tools": {
"batch_slides": {
"limits": [
{
"counter": "batch_slides_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_slides 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 multiple presentation slides in Figma in a single batch call. Much faster than creating slides one at a time. Each slide can be of type: title, content, visual, statement, columns, comparison, or numbered. 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 batch_slides: 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.
batch_slides 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 batch_slides 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 batch_slides. 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.
batch_slides 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.