Get components available in a Figma file
AI agents call get_components to retrieve information from Figma without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists Figma components without creating, modifying, deleting, or executing any operations. It is a read-only query of design assets, posing minimal risk even if accessed by an untrusted agent.
From the tool's definition Tool name 'get_components' and description 'Get components available in a Figma file' indicate data retrieval with no modification or execution. The server overview confirms read-only operations like 'Access all figma components'.
Documented attack patterns abuse exactly the kind of access get_components gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma, and nothing reaches the server without passing your rules. This is the rule we recommend for get_components:
{
"version": "1",
"default": "deny",
"tools": {
"get_components": {}
}
}get_components is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get components available in a Figma file. It is categorised as a Read tool in the Figma MCP Server, which means it retrieves data without modifying state.
Register the Figma MCP server in PolicyLayer and add a rule for get_components: 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. Nothing to install.
get_components 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_components 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_components. 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_components is provided by the Figma MCP server (jayzeedesign/figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma, 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.
3 Figma tools catalogued and risk-classified — across an index of 43,000+ MCP servers.