Get components in a team
AI agents call figma_get_team_components 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 components for |
before | number | — | Cursor indicating which id before which to start retrieving components for |
teamId | string | — | The ID of the team to get components 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 retrieves design components from a Figma team workspace. It performs a query operation that retrieves data without creating, modifying, deleting, executing code, or moving money. The read-only nature and lack of side effects make this a Read category tool with low severity, as exposing team component information poses minimal risk compared to write or destructive operations.
From the tool's definition Tool name is 'figma_get_team_components' and description states 'Get components in a team'. The verb 'Get' and the action of retrieving/querying components without modification indicates a read operation.
Attacks that exploit this kind of access
Get components 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_components 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_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 MCP Server. Nothing to install.
figma_get_team_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 figma_get_team_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 figma_get_team_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.
figma_get_team_components 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 →