generate_responsive_variant · Stitch MCP Server MCP

WHAT IT DOES

What generate_responsive_variant does on Stitch MCP Server

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

This tool creates new design assets (responsive variants) reversibly within the Stitch design system. It does not execute arbitrary code, delete data, or trigger financial operations. While it generates multiple screen variants, these are design artifacts that can be modified or removed, making it a Write operation.

From the tool's definition Tool description states it 'Creates a responsive variant' which is a create operation that generates new design artifacts. The tool modifies the design system by adding new responsive variants without destroying existing content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_responsive_variant Rate-limited

generate_responsive_variant 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_responsive_variant": {
      "limits": [
        {
          "counter": "generate_responsive_variant_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 generate_responsive_variant

What does the generate_responsive_variant tool do? +

Creates a responsive variant of an existing screen for a different device type while maintaining the same 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 generate_responsive_variant? +

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

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

Can I rate-limit generate_responsive_variant? +

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

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

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