generate_mfe_module · Figma React MCP: Risk & Policy

WHAT IT DOES

What generate_mfe_module does on Figma React

AI agents use generate_mfe_module to create or update resources in Figma React — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma React environment.

WHY IT NEEDS A POLICY

Why generate_mfe_module needs a policy

This tool creates new code artifacts (micro-frontend modules) and modifies the widget registry by adding entries. These are reversible write operations—the generated modules and registry entries can be deleted or replaced. It does not execute arbitrary commands (Execute), permanently destroy data (Destructive), or involve financial transactions (Financial).

From the tool's definition Tool description states it 'Generate[s] a self-contained micro-frontend module' and creates 'a widget registry entry.' The verbs 'generate' and the creation of new module artifacts and registry entries indicate data creation/modification rather than retrieval…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_mfe_module Rate-limited

generate_mfe_module stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_mfe_module": {
      "limits": [
        {
          "counter": "generate_mfe_module_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Figma React, so you can run agents against it safely.

FAQ

Questions about generate_mfe_module

What does the generate_mfe_module tool do? +

Generate a self-contained micro-frontend module from a Figma node, with mount/unmount lifecycle hooks and a widget registry entry. It is categorised as a Write tool in the Figma React MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_mfe_module? +

Register the Figma React MCP server in PolicyLayer and add a rule for generate_mfe_module: 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 React. Nothing to install.

What risk level is generate_mfe_module? +

generate_mfe_module is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_mfe_module? +

Yes. Add a rate_limit block to the generate_mfe_module 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.

How do I block generate_mfe_module completely? +

Set action: deny in the PolicyLayer policy for generate_mfe_module. 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.

What MCP server provides generate_mfe_module? +

generate_mfe_module is provided by the Figma React MCP server (manansingh2001/figma-react-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.