chromewebstore_permissions
Retrieve a Chrome Web Store item's declared permissions. Returns the permissions a Chrome Web Store extension declares in its manifest: permissions, optional_permissions, host_permissions, optional_host_permissions, plus manifest_version and min_browser_version. Useful for security and supply-cha...
This record as markdown: /tools/crawlora-mcp/chromewebstore-permissions.md
What chromewebstore_permissions does on Crawlora
AI agents call chromewebstore_permissions 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 id) |
lang | string | — | Two-letter language code |
country | string | — | Two-letter storefront country code |
Parameters from the server's own tool schema.
Why chromewebstore_permissions is rated Low
Even though chromewebstore_permissions 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_permissions 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_permissions, this is the rule to start with:
chromewebstore_permissions 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_permissions call is checked against it from then on.
Questions about chromewebstore_permissions
Retrieve a Chrome Web Store item's declared permissions. Returns the permissions a Chrome Web Store extension declares in its manifest: permissions, optional_permissions, host_permissions, optional_host_permissions, plus manifest_version and min_browser_version. Useful for security and supply-chain review. 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_permissions 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_permissions: 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_permissions 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_permissions 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_permissions. 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_permissions 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