# update_design_system

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.

Agent View of the PolicyLayer registry record for `update_design_system`. HTML page: https://policylayer.com/tools/com-googleapis-stitch-mcp/update-design-system

## Facts

- Tool: `update_design_system`
- Server: Mcp (`https://stitch.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-stitch-mcp.md
- Homepage: https://github.com/https://stitch.googleapis.com/mcp
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (3 required)
- Recommended policy verdict: Rate-limited

## Parameters

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

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_design_system",
    "arguments": {
      "name": "<name>",
      "projectId": "<projectId>",
      "designSystem": {}
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_design_system": {
      "limits": [
        {
          "counter": "update_design_system_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp (14)

- `delete_project` — Destructive — https://policylayer.com/tools/com-googleapis-stitch-mcp/delete-project.md
- `get_project` — Read — https://policylayer.com/tools/com-googleapis-stitch-mcp/get-project.md
- `get_screen` — Read — https://policylayer.com/tools/com-googleapis-stitch-mcp/get-screen.md
- `list_design_systems` — Read — https://policylayer.com/tools/com-googleapis-stitch-mcp/list-design-systems.md
- `list_projects` — Read — https://policylayer.com/tools/com-googleapis-stitch-mcp/list-projects.md
- `list_screens` — Read — https://policylayer.com/tools/com-googleapis-stitch-mcp/list-screens.md
- `apply_design_system` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/apply-design-system.md
- `create_design_system` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/create-design-system.md
- `create_design_system_from_design_md` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/create-design-system-from-design-md.md
- `create_project` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/create-project.md
- `edit_screens` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/edit-screens.md
- `generate_screen_from_text` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/generate-screen-from-text.md
- `generate_variants` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/generate-variants.md
- `upload_design_md` — Write — https://policylayer.com/tools/com-googleapis-stitch-mcp/upload-design-md.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-googleapis-stitch-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-stitch-mcp