Set focus on a specific node in Figma by selecting it and scrolling viewport to it
AI agents invoke set_focus to trigger actions in Figma AI Bridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers external operations in Figma (selecting a node and scrolling the viewport), which are UI/application control actions. It doesn't purely read data, nor does it create, modify, or delete content. It controls the Figma application state (selection and viewport position), making it an Execute-category action. Blast radius is low as it only affects the view/selection state.
From the tool's definition 'Set focus on a specific node in Figma by selecting it and scrolling viewport to it'
Documented attack patterns abuse exactly the kind of access set_focus 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_focus:
{
"version": "1",
"default": "deny",
"tools": {
"set_focus": {
"limits": [
{
"counter": "set_focus_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_focus stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set focus on a specific node in Figma by selecting it and scrolling viewport to it. It is categorised as a Execute tool in the Figma AI Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Figma AI Bridge MCP server in PolicyLayer and add a rule for set_focus: 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_focus is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_focus 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_focus. 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_focus 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.