deploy-percentage

Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher than the current target. Only available for items with 10,000+ seven-day active users.

SERVERCws SOURCE@1llum1n4t1/cws-mcp

High RISK CLASS

Category Execute

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/1llum1n4t1-cws-mcp/deploy-percentage.md

WHAT IT DOES

What deploy-percentage does on Cws

AI agents invoke deploy-percentage to trigger actions in Cws. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`itemId`	string	—	Extension item ID (defaults to CWS_ITEM_ID env var)
`percentage`	number	Yes	Deploy percentage (0-100). Must be larger than the current target percentage.
`publisherId`	string	—	Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')

Parameters from the server's own tool schema.

RISK

Why deploy-percentage is rated High

This tool triggers an external operation (Chrome Web Store staged rollout percentage change) whose effects depend on arguments (the percentage value). While it modifies deployment state, it is not strictly destructive (reversible via lower percentage) and not financial. It is Execute because it commits a concrete action to production infrastructure affecting end-user availability.

From the tool's definition Tool name 'deploy-percentage' and description 'Set the published deploy percentage for staged rollout on Chrome Web Store' indicates it executes a deployment action that changes the live distribution of an extension to real users.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

deploy-percentage Rate-limited

deploy-percentage stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy-percentage": {
      "limits": [
        {
          "counter": "deploy-percentage_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about deploy-percentage

What does the deploy-percentage tool do? +

Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher than the current target. Only available for items with 10,000+ seven-day active users. It is categorised as a Execute tool in the Cws MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does deploy-percentage accept? +

deploy-percentage accepts 3 parameters: itemId, percentage, publisherId. Required: percentage. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on deploy-percentage? +

Register the Cws MCP server in PolicyLayer and add a rule for deploy-percentage: 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.

What risk level is deploy-percentage? +

deploy-percentage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy-percentage? +

Yes. Add a rate_limit block to the deploy-percentage 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 deploy-percentage completely? +

Set action: deny in the PolicyLayer policy for deploy-percentage. 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 deploy-percentage? +

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

KEEP EXPLORING

More on Cws, and thousands of servers like it.

This server

All 8 Cws tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →