datasets_chrome_extensions_history
Get Chrome Web Store item history. Returns chronological change-only observations for a Chrome Web Store item.
This record as markdown: /tools/crawlora-mcp/datasets-chrome-extensions-history.md
What datasets_chrome_extensions_history does on Crawlora
AI agents call datasets_chrome_extensions_history 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 |
|---|---|---|---|
id | string | Yes | Chrome Web Store item id |
to | string | — | Inclusive end date, YYYY-MM-DD |
from | string | — | Inclusive start date, YYYY-MM-DD |
limit | integer | — | Maximum points, default 365, max 1000 |
Parameters from the server's own tool schema.
Why datasets_chrome_extensions_history is rated Low
Even though datasets_chrome_extensions_history 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 datasets_chrome_extensions_history 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_history, this is the rule to start with:
datasets_chrome_extensions_history 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_history call is checked against it from then on.
Questions about datasets_chrome_extensions_history
Get Chrome Web Store item history. Returns chronological change-only observations for a Chrome Web Store item. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_chrome_extensions_history accepts 4 parameters: id, to, from, limit. Required: id. 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_history: 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_history 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_history 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_history. 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_history 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