get_selection
AI agents call get_selection to retrieve information from Figma MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves the current selection state from Figma, which is a read-only query operation. It does not create, modify, delete, or execute external operations. Even though the description is empty, the tool name and sibling tools (which include obvious side-effect operations like 'create_frame_in_figma', 'create_arc', etc.) indicate this is a data-retrieval function.
From the tool's definition Tool name 'get_selection' indicates retrieval of currently selected objects in Figma. The sibling tools context shows this is a Figma design API server where 'get_selection' follows a pattern of querying/retrieving state (similar to 'check_connection',…
Attacks that exploit this kind of access
get_selection. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Figma MCP Server 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 MCP Server. Nothing to install.
get_selection is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_selection is provided by the Figma MCP Server MCP server (sichang824/mcp-figma). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →