chromewebstore_category
List items in a Chrome Web Store category. Returns the item cards listed under an extensions category slug (e.g. productivity/tools, lifestyle/shopping, make_chrome_yours/privacy). Use /chromewebstore/categories for the reference taxonomy. Defaults: num=50, country=us, lang=en.
This record as markdown: /tools/crawlora-mcp/chromewebstore-category.md
What chromewebstore_category does on Crawlora
AI agents call chromewebstore_category 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 |
category | string | Yes | Category slug under extensions |
Parameters from the server's own tool schema.
Why chromewebstore_category is rated Low
Even though chromewebstore_category 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 chromewebstore_category 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_category, this is the rule to start with:
chromewebstore_category 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_category call is checked against it from then on.
Questions about chromewebstore_category
List items in a Chrome Web Store category. Returns the item cards listed under an extensions category slug (e.g. productivity/tools, lifestyle/shopping, make_chrome_yours/privacy). Use /chromewebstore/categories for the reference taxonomy. 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_category accepts 4 parameters: num, lang, country, category. Required: category. 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_category: 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_category 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_category 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_category. 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_category 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