Generate clean React component with TypeScript - works with plugin data or Figma API
AI agents call get_react_component to retrieve information from Sunnyside Figma MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves design information and generates code output, which is fundamentally a read operation. There are no side effects on Figma data, no code execution in external systems, no data deletion, and no financial implications. The output (generated React code) is new content derived from existing designs but does not modify any persistent state.
From the tool's definition Tool generates (reads and transforms) React components from existing Figma design data; the description states 'Generate clean React component' which indicates code generation from design sources without modifying the underlying Figma file or design system.
Documented attack patterns abuse exactly the kind of access get_react_component gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sunnyside Figma MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_react_component:
{
"version": "1",
"default": "deny",
"tools": {
"get_react_component": {}
}
}get_react_component 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.
Generate clean React component with TypeScript - works with plugin data or Figma API. It is categorised as a Read tool in the Sunnyside Figma MCP MCP Server, which means it retrieves data without modifying state.
Register the Sunnyside Figma MCP server in PolicyLayer and add a rule for get_react_component: 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 Sunnyside Figma MCP. Nothing to install.
get_react_component 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_react_component 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_react_component. 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_react_component is provided by the Sunnyside Figma MCP server (tercumantanumut/sunnysidefigma-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Sunnyside Figma MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
31 Sunnyside Figma MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.