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.
This record as markdown: /tools/1llum1n4t1-cws-mcp/get.md
What get does on Cws
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
itemId | string | — | Extension item ID (defaults to CWS_ITEM_ID env var) |
projection | string | — | Metadata projection to fetch (defaults to DRAFT) |
Parameters from the server's own tool schema.
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.
Attacks that exploit this kind of access
The rule that runs get 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 get, this is the rule to start with:
get 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 get call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Cws MCP Server, which means it retrieves data without modifying state.
get accepts 2 parameters: itemId, projection. 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 get: 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.
get 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 get 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 get. 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.
get 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