datasets_chrome_extensions_metrics
Get Chrome Web Store dataset metrics. Returns chart-ready coverage, adoption, rating, permission, privacy and recent-change aggregates for the stored Chrome Web Store dataset. Days enum: 7, 30, 90.
This record as markdown: /tools/crawlora-mcp/datasets-chrome-extensions-metrics.md
What datasets_chrome_extensions_metrics does on Crawlora
AI agents call datasets_chrome_extensions_metrics 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 |
|---|---|---|---|
days | integer | — | Recent-change window enum: 7, 30, 90; default 30 |
limit | integer | — | Top category and permission buckets, default 10, min 5, max 25 |
Parameters from the server's own tool schema.
Why datasets_chrome_extensions_metrics is rated Low
This tool retrieves pre-computed metrics and aggregates from a Chrome Web Store dataset. It queries and returns read-only statistics (coverage, adoption, rating, permission, privacy data) without performing side effects, executing commands, modifying data, or creating financial obligations. The blast radius of misuse is minimal—an agent could only retrieve existing aggregate data about Chrome extensions.
From the tool's definition Tool description states it 'Returns...aggregates' for a dataset. The verbs 'Get' and 'Returns' indicate data retrieval with no modification. The parameter 'Days enum' suggests filtering/querying a stored dataset, not executing operations or modifying data.
Attacks that exploit this kind of access
The rule that runs datasets_chrome_extensions_metrics 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_metrics, this is the rule to start with:
datasets_chrome_extensions_metrics 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_metrics call is checked against it from then on.
Questions about datasets_chrome_extensions_metrics
Get Chrome Web Store dataset metrics. Returns chart-ready coverage, adoption, rating, permission, privacy and recent-change aggregates for the stored Chrome Web Store dataset. Days enum: 7, 30, 90. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_chrome_extensions_metrics accepts 2 parameters: days, limit. 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_metrics: 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_metrics 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_metrics 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_metrics. 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_metrics 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