# update-metadata

Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports common fields and a raw metadata payload. Note: the v1.1 API is deprecated and will be removed after 2026-10-15; after that, listing changes must be made in the Developer Dashboard.

Agent View of the PolicyLayer registry record for `update-metadata`. HTML page: https://policylayer.com/tools/1llum1n4t1-cws-mcp/update-metadata

## Facts

- Tool: `update-metadata`
- Server: Cws (`@1llum1n4t1/cws-mcp`) — https://policylayer.com/tools/1llum1n4t1-cws-mcp.md
- Install: `npx -y @1llum1n4t1/cws-mcp`
- Homepage: https://www.npmjs.com/package/@1llum1n4t1/cws-mcp
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 9
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `title` | string | no | Store listing title |
| `itemId` | string | no | Extension item ID (defaults to CWS_ITEM_ID env var) |
| `summary` | string | no | Store listing short summary |
| `category` | string | no | Category (e.g. 'productivity', 'developer_tools') |
| `metadata` | object | no | Raw metadata object forwarded as-is to the v1.1 API. Useful for fields not exposed as first-class params. |
| `supportUrl` | string | no | Support URL |
| `description` | string | no | Store listing description |
| `homepageUrl` | string | no | Homepage URL |
| `defaultLocale` | string | no | Default locale (e.g. 'ko', 'en') |

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-metadata",
    "arguments": {}
  }
}
```

## Why update-metadata is rated Medium

An AI agent can call update-metadata faster than any human can review: one bad instruction and it creates or modifies resources in Cws by the hundred, each call as confident as the last.

## Use case

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

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-metadata": {
      "limits": [
        {
          "counter": "update-metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Cws (7)

- `deploy-percentage` — Execute — https://policylayer.com/tools/1llum1n4t1-cws-mcp/deploy-percentage.md
- `get` — Read — https://policylayer.com/tools/1llum1n4t1-cws-mcp/get.md
- `status` — Read — https://policylayer.com/tools/1llum1n4t1-cws-mcp/status.md
- `cancel` — Write — https://policylayer.com/tools/1llum1n4t1-cws-mcp/cancel.md
- `publish` — Write — https://policylayer.com/tools/1llum1n4t1-cws-mcp/publish.md
- `submit` — Write — https://policylayer.com/tools/1llum1n4t1-cws-mcp/submit.md
- `upload` — Write — https://policylayer.com/tools/1llum1n4t1-cws-mcp/upload.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=1llum1n4t1-cws-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1llum1n4t1-cws-mcp