# get

Get the current metadata of a Chrome Web Store item (v1.1 API). Returns title, description, category, and other listing fields. Note: the v1.1 API is deprecated and will be removed after 2026-10-15.

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

## Facts

- Tool: `get`
- 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) |
| `projection` | string | no | Metadata projection to fetch (defaults to DRAFT) |

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

## Why get is rated Low

Even though get only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get 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": {
    "get": {}
  }
}
```

## Other tools on Cws (7)

- `deploy-percentage` — Execute — https://policylayer.com/tools/1llum1n4t1-cws-mcp/deploy-percentage.md
- `status` — Read — https://policylayer.com/tools/1llum1n4t1-cws-mcp/status.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