screen_to_react · Stitch MCP Server MCP: Risk & Policy

WHAT IT DOES

What screen_to_react does on Stitch MCP Server

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

WHY IT NEEDS A POLICY

Why screen_to_react needs a policy

This tool generates/creates code output (React components) from design screens, which is a reversible write operation. While the output is code (which could theoretically be executed), the tool itself only generates or converts designs to code — execution is a separate step.

From the tool's definition Tool name 'screen_to_react' and description 'Converts a Stitch screen' indicates code generation that creates or produces new React code artifacts from design inputs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

screen_to_react Rate-limited

screen_to_react 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": {
    "screen_to_react": {
      "limits": [
        {
          "counter": "screen_to_react_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 Stitch MCP Server, so you can run agents against it safely.

FAQ

Questions about screen_to_react

What does the screen_to_react tool do? +

Converts a Stitch screen. It is categorised as a Write tool in the Stitch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on screen_to_react? +

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

What risk level is screen_to_react? +

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

Can I rate-limit screen_to_react? +

Yes. Add a rate_limit block to the screen_to_react 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 screen_to_react completely? +

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

screen_to_react is provided by the Stitch MCP Server MCP server (oogleyskr/stitch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.