# 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.

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

## Facts

- Tool: `status`
- 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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `itemId` | string | no | Extension item ID (defaults to CWS_ITEM_ID env var) |
| `publisherId` | string | no | Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me') |

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

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "status": {}
  }
}
```

## 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
- `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
- `update-metadata` — Write — https://policylayer.com/tools/1llum1n4t1-cws-mcp/update-metadata.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