edit_screens
Edits existing screens within a project using 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 call fails due to connection error, the process may still succeed.
This record as markdown: /tools/com-googleapis-stitch-mcp/edit-screens.md
What edit_screens does on Mcp
AI agents use edit_screens 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 of screens to edit, example: '4044680601076201931', without the `projects/` prefix. |
deviceType | string | — | Optional. The type of device that captured the screenshot, e.g., mobile or desktop. |
selectedScreenIds | array | Yes | Required. The screen IDs of screens to edit, example: ['98b50e2ddc9943efb387052637738f61', '98b50e2ddc9943efb387052637738f62'], without the `screens/` prefix. |
Parameters from the server's own tool schema.
Why edit_screens is rated Medium
An AI agent can call edit_screens 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.
Attacks that exploit this kind of access
The rule that runs edit_screens 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 edit_screens, this is the rule to start with:
edit_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every edit_screens call is checked against it from then on.
Questions about edit_screens
Edits existing screens within a project using 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 call fails due to connection error, the process may still succeed. 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.
edit_screens accepts 5 parameters: prompt, modelId, projectId, deviceType, selectedScreenIds. Required: prompt, projectId, selectedScreenIds. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for edit_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 Mcp. Nothing to install.
edit_screens 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 edit_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.
Set action: deny in the PolicyLayer policy for edit_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.
edit_screens 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.
More on , and thousands of servers like it.
This server
Across the catalogue