chromewebstore_collection
List items in a curated Chrome Web Store collection. Returns the item cards in a curated store collection slug (e.g. editors_picks_extensions, dark_mode, ai_productivity). Use /chromewebstore/categories for known collection slugs. Defaults: num=50, country=us, lang=en.
This record as markdown: /tools/crawlora-mcp/chromewebstore-collection.md
What chromewebstore_collection does on Crawlora
AI agents call chromewebstore_collection to retrieve information from Crawlora 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 |
|---|---|---|---|
num | integer | — | Maximum number of items |
lang | string | — | Two-letter language code |
country | string | — | Two-letter storefront country code |
collection | string | Yes | Curated collection slug |
Parameters from the server's own tool schema.
Why chromewebstore_collection is rated Low
The tool queries and retrieves publicly available Chrome Web Store collection data. It has no side effects, does not modify data, execute code, delete anything, or involve financial transactions. It is a straightforward read-only data retrieval operation.
From the tool's definition Tool description states 'List items' and 'Returns the item cards in a curated store collection slug'. This is a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs chromewebstore_collection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chromewebstore_collection, this is the rule to start with:
chromewebstore_collection 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 Crawlora, apply this rule, and every chromewebstore_collection call is checked against it from then on.
Questions about chromewebstore_collection
List items in a curated Chrome Web Store collection. Returns the item cards in a curated store collection slug (e.g. editors_picks_extensions, dark_mode, ai_productivity). Use /chromewebstore/categories for known collection slugs. Defaults: num=50, country=us, lang=en. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
chromewebstore_collection accepts 4 parameters: num, lang, country, collection. Required: collection. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for chromewebstore_collection: 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 Crawlora. Nothing to install.
chromewebstore_collection 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 chromewebstore_collection 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 chromewebstore_collection. 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.
chromewebstore_collection is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue