List all variants in a Figma component set to help with variant selection
AI agents call list_component_variants to retrieve information from Figma to Flutter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents information about existing Figma design components without modifying, executing, or deleting anything. It is purely informational and supports the analysis phase of design-to-code conversion. The blast radius of misuse is minimal—worst case, an agent retrieves a list of variant names it didn't need.
From the tool's definition The tool 'list_component_variants' is described as listing variants in a Figma component set. The verb 'list' and the action of retrieving/enumerating component variants constitutes a read-only query with no side effects.
Documented attack patterns abuse exactly the kind of access list_component_variants gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma to Flutter MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_component_variants:
{
"version": "1",
"default": "deny",
"tools": {
"list_component_variants": {}
}
} list_component_variants 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.
List all variants in a Figma component set to help with variant selection. It is categorised as a Read tool in the Figma to Flutter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Figma to Flutter MCP Server MCP server in PolicyLayer and add a rule for list_component_variants: 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 to Flutter MCP Server. Nothing to install.
list_component_variants 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 list_component_variants 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 list_component_variants. 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.
list_component_variants is provided by the Figma to Flutter MCP Server MCP server (mhmzdev/figma-flutter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma to Flutter MCP Server, 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.
13 Figma to Flutter MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.