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.
This record as markdown: /tools/1llum1n4t1-cws-mcp/update-metadata.md
What update-metadata does on Cws
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | — | Store listing title |
itemId | string | — | Extension item ID (defaults to CWS_ITEM_ID env var) |
summary | string | — | Store listing short summary |
category | string | — | Category (e.g. 'productivity', 'developer_tools') |
metadata | object | — | Raw metadata object forwarded as-is to the v1.1 API. Useful for fields not exposed as first-class params. |
supportUrl | string | — | Support URL |
description | string | — | Store listing description |
homepageUrl | string | — | Homepage URL |
defaultLocale | string | — | Default locale (e.g. 'ko', 'en') |
Parameters from the server's own tool schema.
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.
Attacks that exploit this kind of access
The rule that runs update-metadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cws, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update-metadata, this is the rule to start with:
update-metadata 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cws, apply this rule, and every update-metadata call is checked against it from then on.
Questions about 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. It is categorised as a Write tool in the Cws MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update-metadata accepts 9 parameters: title, itemId, summary, category, metadata, supportUrl, description, homepageUrl, defaultLocale. The full parameter table on this page comes from the server's own tool schema.
Register the Cws MCP server in PolicyLayer and add a rule for update-metadata: 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 Cws. Nothing to install.
update-metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-metadata 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.
Set action: deny in the PolicyLayer policy for update-metadata. 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.
update-metadata is provided by the Cws MCP server (@1llum1n4t1/cws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cws, and thousands of servers like it.
This server
Across the catalogue