Switch to a specific page in the Figma document
AI agents use set_current_page 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.
Switching the active/current page in a Figma document modifies the document's view state. It is reversible (you can switch back) and does not delete or create content, making it a Write action. The blast radius is low since it only changes navigation state.
From the tool's definition Switch to a specific page in the Figma document
Documented attack patterns abuse exactly the kind of access set_current_page 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 set_current_page:
{
"version": "1",
"default": "deny",
"tools": {
"set_current_page": {
"limits": [
{
"counter": "set_current_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_current_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.
Switch to a specific page in the Figma document. 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 set_current_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 AI Bridge. Nothing to install.
set_current_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 set_current_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 set_current_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.
set_current_page 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.