chromewebstore_developer
Retrieve a Chrome Web Store publisher and their items. Returns a Chrome Web Store publisher (developer) by publisher id, including the disclosed trader details — legal name, email, phone, address, website, and D-U-N-S number — plus the publisher's listed items ("More from ..."). Trader fields are...
This record as markdown: /tools/crawlora-mcp/chromewebstore-developer.md
What chromewebstore_developer does on Crawlora
AI agents call chromewebstore_developer 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 publisher id (u + 32 hex chars) |
num | integer | — | Maximum number of items |
lang | string | — | Two-letter language code |
country | string | — | Two-letter storefront country code |
Parameters from the server's own tool schema.
Why chromewebstore_developer is rated Low
This tool queries and retrieves publicly available Chrome Web Store publisher information including trader details and listed items. It is a read-only operation that fetches existing data without creating, modifying, deleting, or executing anything.
From the tool's definition Tool description states "Retrieve a Chrome Web Store publisher" and "Returns a Chrome Web Store publisher". The verb "Retrieve" combined with "Returns" indicates data query operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs chromewebstore_developer 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_developer, this is the rule to start with:
chromewebstore_developer 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_developer call is checked against it from then on.
Questions about chromewebstore_developer
Retrieve a Chrome Web Store publisher and their items. Returns a Chrome Web Store publisher (developer) by publisher id, including the disclosed trader details — legal name, email, phone, address, website, and D-U-N-S number — plus the publisher's listed items ("More from ..."). Trader fields are only present for publishers that identify as EU traders. Defaults: num=50, 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_developer accepts 4 parameters: id, num, 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_developer: 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_developer 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_developer 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_developer. 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_developer 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