Get component sets in a team
AI agents call figma_get_team_component_sets 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 |
|---|---|---|---|
after | number | — | Cursor indicating which id after which to start retrieving component sets for |
before | number | — | Cursor indicating which id before which to start retrieving component sets for |
teamId | string | — | The ID of the team to get component sets for |
page_size | number | — | Number of items to return in a paged list of results |
Parameters from the server's own tool schema.
This tool queries and retrieves component set information from a Figma team. It performs a read-only operation with no capacity to modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could only enumerate or view existing design components, which poses no immediate risk to system integrity or data loss.
From the tool's definition Tool name contains 'get' and description states 'Get component sets in a team' — retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get component sets in a team. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.
figma_get_team_component_sets accepts 4 parameters: after, before, teamId, page_size. 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_team_component_sets: 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_team_component_sets 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_team_component_sets 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_team_component_sets. 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_team_component_sets 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 →