edit_screens · Stitch MCP Server MCP: Risk & Policy

WHAT IT DOES

What edit_screens does on Stitch MCP Server

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

This tool modifies existing screens based on instructions, which is a Write operation (creates or modifies data reversibly). It does not delete data (not Destructive), does not execute arbitrary code with unpredictable side effects (not Execute), and poses no financial risk (not Financial).

From the tool's definition Tool description states it 'Edits one or more existing screens' — a modify operation on design artifacts. The word 'Edits' indicates reversible modification rather than deletion or execution of arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

edit_screens Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit_screens": {
      "limits": [
        {
          "counter": "edit_screens_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 edit_screens

What does the edit_screens tool do? +

Edits one or more existing screens based on text instructions. 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 edit_screens? +

Register the Stitch MCP Server 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 Stitch MCP Server. Nothing to install.

What risk level is edit_screens? +

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

Can I rate-limit edit_screens? +

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.

How do I block edit_screens completely? +

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.

What MCP server provides edit_screens? +

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