datasets_chrome_extensions_search
Search the Chrome Web Store dataset. Searches stored Chrome Web Store item snapshots. Item type enum: extension, theme, app, unknown. Sort enum: relevance, users_desc, rating_desc, reviews_desc, updated_desc, trending_desc. Status enum: active, removed. Manifest version enum: 2, 3.
This record as markdown: /tools/crawlora-mcp/datasets-chrome-extensions-search.md
What datasets_chrome_extensions_search does on Crawlora
AI agents call datasets_chrome_extensions_search 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 |
|---|---|---|---|
q | string | — | Full-text query, max 256 characters |
page | integer | — | Page number, default 1 |
sort | string | — | Sort enum: relevance, users_desc, rating_desc, reviews_desc, updated_desc, trending_desc |
status | string | — | Status enum: active, removed |
category | string | — | Exact Chrome Web Store category |
developer | string | — | Exact displayed developer name |
item_type | string | — | Item type enum: extension, theme, app, unknown |
min_users | integer | — | Minimum displayed user count |
page_size | integer | — | Page size, default 20, max 100 |
min_rating | number | — | Minimum rating, 0 through 5 |
permission | string | — | Exact declared permission |
collects_data | boolean | — | Filter by public data-collection disclosure |
Parameters from the server's own tool schema.
Why datasets_chrome_extensions_search is rated Low
This is a read-only search/query tool that retrieves information from a stored dataset of Chrome Web Store items. It performs no modifications, executions, deletions, or financial transactions. The capability to search and filter data carries minimal risk as it only returns publicly available Chrome Web Store information. Confidence is high due to clear documentation of search-only functionality.
From the tool's definition Tool description explicitly states 'Search the Chrome Web Store dataset' and 'Searches stored Chrome Web Store item snapshots' with enumerated filter options (item type, sort, status, manifest version).
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs datasets_chrome_extensions_search 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 datasets_chrome_extensions_search, this is the rule to start with:
datasets_chrome_extensions_search 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 datasets_chrome_extensions_search call is checked against it from then on.
Questions about datasets_chrome_extensions_search
Search the Chrome Web Store dataset. Searches stored Chrome Web Store item snapshots. Item type enum: extension, theme, app, unknown. Sort enum: relevance, users_desc, rating_desc, reviews_desc, updated_desc, trending_desc. Status enum: active, removed. Manifest version enum: 2, 3. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_chrome_extensions_search accepts 12 parameters: q, page, sort, status, category, developer, item_type, min_users, page_size, min_rating, permission, collects_data. 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 datasets_chrome_extensions_search: 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.
datasets_chrome_extensions_search 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 datasets_chrome_extensions_search 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 datasets_chrome_extensions_search. 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.
datasets_chrome_extensions_search 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