Low Risk

get_selection

Get information about the current selection in Figma

How to control get_selection ↓

What get_selection does on Figma AI Bridge

AI agents call get_selection to retrieve information from Figma AI Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_selection needs a policy

This tool queries the state of the current selection in Figma without modifying, creating, deleting, or executing any operations. It is a straightforward read operation that returns information about what is currently selected, comparable to a GET request in REST APIs. No data is created, modified, or destroyed, and no external code or commands are executed.

From the tool's definition Tool name 'get_selection' and description 'Get information about the current selection in Figma' indicate a retrieval operation with no side effects.

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

How to control get_selection

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_selection": {}
  }
}

get_selection is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_selection

What does the get_selection tool do? +

Get information about the current selection in Figma. It is categorised as a Read tool in the Figma AI Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_selection? +

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

get_selection is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_selection? +

Yes. Add a rate_limit block to the get_selection 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 get_selection completely? +

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

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

Free to start. No card required.

64 Figma AI Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.