Generates a new screen from a text prompt describing the desired UI.
AI agents use generate_screen_from_text 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 new design assets (screens) in the workspace, which is a reversible write operation. While the generation is AI-driven and the output quality depends on the prompt, the core action is creating and persisting new data in the design project.
From the tool's definition Tool generates or creates a new screen artifact from a text prompt - this is a CREATE operation that modifies the design workspace by adding new content.
Attacks that exploit this kind of access
Generates a new screen from a text prompt describing the desired UI. 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_screen_from_text: 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_screen_from_text 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_screen_from_text 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_screen_from_text. 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_screen_from_text 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 →