generate_screen_from_text

SERVERMcp SOURCEhttps://stitch.googleapis.com/mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-stitch-mcp/generate-screen-from-text.md

WHAT IT DOES

What generate_screen_from_text does on Mcp

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

Parameter	Type	Required	Description
`prompt`	string	Yes	Required. The input text to generate the screen from.
`modelId`	string	—	Optional. The model to use for generation.
`projectId`	string	Yes	Required. The project ID to generate the screen for, example: '4044680601076201931', without the `projects/` prefix.
`deviceType`	string	—	The type of device that captured the screenshot, e.g., mobile or desktop.
`designSystem`	string	—	Optional. The design system id to use for generating the new screen, should always be configured for design consistency, via `get_project` or `list_assets` meth

Parameters from the server's own tool schema.

RISK

Why generate_screen_from_text is rated Medium

An AI agent can call generate_screen_from_text faster than any human can review: one bad instruction and it creates or modifies resources in Mcp by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs generate_screen_from_text safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_screen_from_text, this is the rule to start with:

generate_screen_from_text Rate-limited

generate_screen_from_text 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_screen_from_text": {
      "limits": [
        {
          "counter": "generate_screen_from_text_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every generate_screen_from_text call is checked against it from then on.

FAQ

Questions about generate_screen_from_text

What does the generate_screen_from_text tool do? +

Generates a new screen within a project from a text prompt. Instructions for Tool Call: * This action can take a few minutes to complete. Please be patient. DO NOT RETRY. * If the tool fails with a timeout, don't retry. Instead, try to get the screen with get_screen method every 30 seconds for up to 10 times before giving up. * If the tool call fails due to connection error, the generation process may still succeed. Please try to get the screen with get_screen method later. Output: * output_components: If output_components contains text, return it to the user. If output_components contains suggestions (e.g. "Yes, make them all"), present these suggestions to the user. If the user accepts one of the suggestions, call generate_screen_from_text again with prompt set to the accepted suggestion. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does generate_screen_from_text accept? +

generate_screen_from_text accepts 5 parameters: prompt, modelId, projectId, deviceType, designSystem. Required: prompt, projectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_screen_from_text? +

Register the 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 Mcp. Nothing to install.

What risk level is generate_screen_from_text? +

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

Can I rate-limit generate_screen_from_text? +

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.

How do I block generate_screen_from_text completely? +

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.

What MCP server provides generate_screen_from_text? +

generate_screen_from_text is provided by the MCP server (https://stitch.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 15 tools →

Across the catalogue

generate_screen on Stitch MCP Server →generate_commit on MCP Server PR Pilot →generate_summary on ACE-MCP →generate_video_title on YouTube MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →