Get comprehensive status report of the cached style library
AI agents call style_library_status 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 reports status information about an already-cached style library. It performs a read-only query operation with no side effects, no code execution, no data modification, and no irreversible actions. The blast radius of misuse is minimal—at worst, an agent could read cached styling information that may already be accessible through the Figma API or exported data.
From the tool's definition Tool name 'style_library_status' and description 'Get comprehensive status report of the cached style library' indicate a retrieval/query operation that reports on existing cached data with no modification, execution, or deletion of data.
Documented attack patterns abuse exactly the kind of access style_library_status 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 style_library_status:
{
"version": "1",
"default": "deny",
"tools": {
"style_library_status": {}
}
} style_library_status 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 comprehensive status report of the cached style library. 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 style_library_status: 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.
style_library_status 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 style_library_status 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 style_library_status. 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.
style_library_status 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.