Generates design variants of an existing screen.
AI agents use generate_variants 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.
The tool creates or generates new design variants, which are new data artifacts. This is reversible (variants can be deleted) and has no irreversible consequences. It does not execute arbitrary code, delete data, or move financial resources. It fits the Write category—creating new design assets.
From the tool's definition Tool name 'generate_variants' and description 'Generates design variants of an existing screen' indicate creation of new design assets. This is a write operation that creates new data (design variants) based on existing designs.
Attacks that exploit this kind of access
Generates design variants of an existing 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.
Register the Stitch MCP Server MCP server in PolicyLayer and add a rule for generate_variants: 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.
generate_variants is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_variants 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 generate_variants. 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.
generate_variants 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →