update_design_system

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

Medium RISK CLASS

Category Write

Parameters 33 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/update-design-system.md

WHAT IT DOES

What update_design_system does on Mcp

AI agents use update_design_system 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
`name`	string	Yes	Required. Identifier. The resource name of the design system to update. Format: `assets/{asset_id}` Example: `assets/15996705518239280238`
`projectId`	string	Yes	Required. The project ID to update design system for, example: '4044680601076201931', without the `projects/` prefix.
`designSystem`	object	Yes	Required. The design system to update.

Parameters from the server's own tool schema.

RISK

Why update_design_system is rated Medium

This tool creates or modifies design system configurations reversibly. Changes to design tokens, color palettes, typography, and appearance settings are stored modifications that can be edited or reverted. While it affects the visual foundation of a project, these are not irreversible deletions (Destructive), nor do they execute arbitrary code (Execute) or move money (Financial).

From the tool's definition Tool description states it 'Updates a design system' and involves 'change the overall visual theme, style, or branding' including configurable properties like Color Palette, Typography, Shape, and Appearance.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_design_system 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 update_design_system, this is the rule to start with:

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.

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

FAQ

Questions about update_design_system

What does the update_design_system tool do? +

Updates a design system for a project. Use this tool when the user wants to change the overall visual theme, style, or branding of the application. This includes configuring: - Color Palette: Presets, custom primary colors, and saturation levels. - Typography: Font families (e.g., Inter, Roboto, etc.). - Shape: Corner roundness for UI elements. - Appearance: Light and dark mode background colors. - Design MD: Free-form design instructions in markdown. This tool establishes the foundational design tokens that apply across all screens in the project. 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 update_design_system accept? +

update_design_system accepts 3 parameters: name, projectId, designSystem. Required: name, projectId, designSystem. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_design_system? +

Register the 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 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 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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