AI agents call get_components to retrieve information from Figmad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple query operation to retrieve metadata about Figma components. It does not modify, delete, or execute any operations—it only reads and returns existing data (keys, names, descriptions). This is a typical Read category action with minimal security risk.
From the tool's definition Tool name 'get_components' combined with description 'List all components in a Figma file. Returns component keys, names, and descriptions' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all components in a Figma file. Returns component keys, names, and descriptions. It is categorised as a Read tool in the Figmad MCP Server, which means it retrieves data without modifying state.
Register the Figmad 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 Figmad. 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 Figmad MCP server (toro1221/figmad-mcp). 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 →