chromewebstore_privacy
Retrieve a Chrome Web Store item's privacy disclosures. Returns an extension's privacy disclosures as the store renders them: the developer's data-use statement, whether it collects data, the standard data-handling declarations, and the privacy-policy link. Defaults: country=us, lang=en.
This record as markdown: /tools/crawlora-mcp/chromewebstore-privacy.md
What chromewebstore_privacy does on Crawlora
AI agents call chromewebstore_privacy 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 (32-character extension/theme id) |
lang | string | — | Two-letter language code |
country | string | — | Two-letter storefront country code |
Parameters from the server's own tool schema.
Why chromewebstore_privacy is rated Low
This tool queries and retrieves publicly available privacy disclosure information from the Chrome Web Store. It performs a GET-like operation with no ability to modify, delete, or execute anything. The tool simply presents existing information as rendered by the store. No side effects, no data mutation, no code execution.
From the tool's definition Tool description explicitly states it 'Retrieve[s]' privacy disclosures and 'Returns' data about an extension's privacy information. Keywords: 'retrieve', 'returns' indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs chromewebstore_privacy 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_privacy, this is the rule to start with:
chromewebstore_privacy 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_privacy call is checked against it from then on.
Questions about chromewebstore_privacy
Retrieve a Chrome Web Store item's privacy disclosures. Returns an extension's privacy disclosures as the store renders them: the developer's data-use statement, whether it collects data, the standard data-handling declarations, and the privacy-policy link. Defaults: 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_privacy accepts 3 parameters: id, lang, country. 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 chromewebstore_privacy: 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_privacy 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_privacy 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_privacy. 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_privacy 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