set_selections

THE RISK

High Risk

Why set_selections needs a policy

This tool actively manipulates the Figma application's UI state by changing the current selection and scrolling the viewport. While it doesn't create, modify, or delete design data, it executes operations against an external application that affect its runtime state. It goes beyond a pure read operation since it causes side effects (changed selection state, viewport scroll) in the Figma environment.

From the tool's definition 'Set selection to multiple nodes in Figma and scroll viewport to show them' — triggers a UI state change (selection) and viewport manipulation in an external application (Figma)

Documented attack patterns abuse exactly the kind of access set_selections gives an agent:

POLICY

How to control set_selections

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_selections:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_selections": {
      "limits": [
        {
          "counter": "set_selections_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

set_selections 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.

Create a free account and register Figma AI Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Figma AI Bridge tools

Destructive delete_multiple_nodes Delete multiple nodes from Figma at once Destructive delete_node Delete a node from Figma Execute set_focus Set focus on a specific node in Figma by selecting it and scrolling viewport to it Write batch_slides Create multiple presentation slides in Figma in a single batch call. Much faster than crea Write bind_variable_to_fill Bind a design token variable to a node Write bind_variable_to_stroke Bind a design token variable to a node Write clone_node Clone an existing node in Figma Write create_component_instance Create an instance of a component in Figma

All 64 Figma AI Bridge tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Figma AI Bridge → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about set_selections

What does the set_selections tool do? +

Set selection to multiple nodes in Figma and scroll viewport to show them. 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.

How do I enforce a policy on set_selections? +

Register the Figma AI Bridge MCP server in PolicyLayer and add a rule for set_selections: 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.

What risk level is set_selections? +

set_selections is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_selections? +

Yes. Add a rate_limit block to the set_selections 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.

How do I block set_selections completely? +

Set action: deny in the PolicyLayer policy for set_selections. 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.

What MCP server provides set_selections? +

set_selections 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.

Enforce policy on every Figma AI Bridge tool call.

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.

CHECK YOUR STACK →