Get a component by key
AI agents call figma_get_component 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | — | The key of the component to get |
Parameters from the server's own tool schema.
This tool retrieves a single component from Figma by its key identifier. It performs a query/fetch operation with no side effects, data modification, deletion, or execution of arbitrary code. The blast radius of misuse is minimal—at worst, an agent could access design components it shouldn't see, which is a confidentiality issue but not operational damage. This is a straightforward read operation.
From the tool's definition Tool name 'figma_get_component' with description 'Get a component by key' indicates a retrieval operation. The verb 'Get' and the absence of any modification language confirm read-only access to design component data.
Attacks that exploit this kind of access
Get a component by key. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.
figma_get_component accepts 1 parameter: key. The full parameter table on this page comes from the server's own tool schema.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for figma_get_component: 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.
figma_get_component 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 figma_get_component 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 figma_get_component. 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.
figma_get_component is provided by the Figma MCP Server MCP server (thirdstrandstudio/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 →