// SCAN REPORT

Cws

8 tools. 6 can modify or destroy data without limits.

6 write tools that can modify data. Rate limits recommended.

Last updated: 27 Sept 2026

6 can modify or destroy data

2 read-only

8 tools total

Community server · catalogue entry checked 06/08/2026 · full schemas captured for 8 of 8 tools

How to control Cws ↓

TOOL MAP

What Cws exposes to your agents

Read (2) Write / Execute (6) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Cws costs in tokens

1,527 tokens of tool definitions, loaded on every request

0.8% of a 200k context window

316 heaviest tool: submit

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Cws tools

Execute · High deploy-percentage This tool triggers an external operation (Chrome Web Store staged rollout percentage change) whose effects depend on arguments (the percentage value). Write · Medium cancel Cancelling a pending submission reverts/stops an in-progress action (a submission under review) rather than deleting data permanently. Write · High upload This tool creates or modifies extension draft data by uploading a ZIP file, which is a reversible change. Write · Medium publish Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, block-on-warnings, and skip

6 of Cws's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Cws

PolicyLayer is an MCP gateway — it sits between your AI agents and Cws, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "cancel": {
    "limits": [
      {
        "counter": "cancel_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get": {
    "limits": [
      {
        "counter": "get_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Cws — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CWS →

Instant setup, no code required.

FULL CATALOGUE

All 8 Cws tools

EXECUTE 1 tools

Execute deploy-percentage Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher

WRITE 5 tools

Write cancel Cancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review. Write publish Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentag Write submit One-shot submission: (optional preflight existence check) → upload the ZIP → verify the upload succeeded → pub Write update-metadata Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports common fields and a raw meta Write upload Upload a ZIP file to update an existing Chrome Web Store item draft. Note: Creating new items via API is not s

READ 2 tools

Read get Get the current metadata of a Chrome Web Store item (v1.1 API). Returns title, description, category, and othe Read status Fetch the current status of an extension on Chrome Web Store. Returns published/submitted revision status, dep

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Cws

How do I prevent bulk modifications through Cws? +

The Cws server has 5 write tools including cancel, publish, submit. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Cws.

How many tools does the Cws MCP server expose? +

8 tools across 4 categories: Destructive, Execute, Read, Write. 2 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Cws? +

Register the Cws MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Cws tool call.

Deterministic rules across all 8 Cws tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CWS →

Instant setup, no code required.

8 Cws tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Cws's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →