update_design_system · Stitch- MCP: Risk & Policy

WHAT IT DOES

What update_design_system does on Stitch-MCP

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

WHY IT NEEDS A POLICY

Why update_design_system needs a policy

This tool creates or modifies design system data within the Stitch platform. While the description is empty (lowering confidence slightly), the name and context clearly indicate a Write operation that alters design system properties or rules. The changes are reversible (can be updated again), so it does not qualify as Destructive.

From the tool's definition Tool name 'update_design_system' indicates modification of design system configuration or assets. Sibling tools like 'create_design_system' and 'apply_design_system' confirm this server manages design systems as modifiable resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_design_system Rate-limited

update_design_system 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": {
    "update_design_system": {
      "limits": [
        {
          "counter": "update_design_system_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, so you can run agents against it safely.

FAQ

Questions about update_design_system

What does the update_design_system tool do? +

update_design_system. It is categorised as a Write tool in the Stitch-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_design_system? +

Register the Stitch- MCP server in PolicyLayer and add a rule for update_design_system: 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. Nothing to install.

What risk level is update_design_system? +

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

Can I rate-limit update_design_system? +

Yes. Add a rate_limit block to the update_design_system 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 update_design_system completely? +

Set action: deny in the PolicyLayer policy for update_design_system. 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 update_design_system? +

update_design_system is provided by the Stitch- MCP server (samueljayasingh/stitchmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.