status
Fetch the current status of an extension on Chrome Web Store. Returns published/submitted revision status, deploy percentage, version, takedown/warning flags, and last upload state.
This record as markdown: /tools/1llum1n4t1-cws-mcp/status.md
What status does on Cws
AI agents call status to retrieve information from Cws without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
itemId | string | — | Extension item ID (defaults to CWS_ITEM_ID env var) |
publisherId | string | — | Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me') |
Parameters from the server's own tool schema.
Why status is rated Low
This tool retrieves metadata and state information about an extension (published status, deploy percentage, version, flags, upload state) with no capability to modify, delete, or execute actions. It is a pure information query with no side effects on the Chrome Web Store or extension data.
From the tool's definition Tool description states it 'Fetch[es] the current status' and 'Returns' information about extension state without modifying anything. The verb 'fetch' and return-only operations indicate a read-only query.
Attacks that exploit this kind of access
The rule that runs status 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 status, this is the rule to start with:
status is read-only, so it stays allowed. 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 status call is checked against it from then on.
Questions about status
Fetch the current status of an extension on Chrome Web Store. Returns published/submitted revision status, deploy percentage, version, takedown/warning flags, and last upload state. It is categorised as a Read tool in the Cws MCP Server, which means it retrieves data without modifying state.
status accepts 2 parameters: itemId, publisherId. 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 status: 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.
status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the status 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 status. 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.
status 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