batch_generate_screens · Stitch MCP Server MCP

WHAT IT DOES

What batch_generate_screens does on Stitch MCP Server

AI agents use batch_generate_screens 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 batch_generate_screens needs a policy

This tool creates new design screens/artifacts. While generation is reversible (screens can be deleted), the operation modifies the design workspace by adding multiple new screens. This is a Write operation rather than Execute because it creates design content following a template/design system rather than executing arbitrary code or commands.

From the tool's definition Tool name 'batch_generate_screens' and description 'Generates multiple related screens in a single operation' indicate content creation and modification operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_generate_screens Rate-limited

batch_generate_screens 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": {
    "batch_generate_screens": {
      "limits": [
        {
          "counter": "batch_generate_screens_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 batch_generate_screens

What does the batch_generate_screens tool do? +

Generates multiple related screens in a single operation with consistent design language. 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 batch_generate_screens? +

Register the Stitch MCP Server MCP server in PolicyLayer and add a rule for batch_generate_screens: 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 batch_generate_screens? +

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

Can I rate-limit batch_generate_screens? +

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

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

batch_generate_screens 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.