appstore_developer
Retrieve apps by developer ID. Returns App Store apps associated with a specific developer artist ID.
This record as markdown: /tools/crawlora-mcp/appstore-developer.md
What appstore_developer does on Crawlora
AI agents call appstore_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 |
|---|---|---|---|
lang | string | — | Result language tag |
dev_id | string | Yes | Developer artist ID |
country | string | — | Two-letter storefront country code |
Parameters from the server's own tool schema.
Why appstore_developer is rated Low
This tool queries and returns publicly available App Store data filtered by developer identifier. It performs a retrieval operation without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could only retrieve app information already publicly available.
From the tool's definition Tool description states 'Retrieve apps by developer ID' and 'Returns App Store apps associated with a specific developer artist ID' — both indicate a read-only query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs appstore_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 appstore_developer, this is the rule to start with:
appstore_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 appstore_developer call is checked against it from then on.
Questions about appstore_developer
Retrieve apps by developer ID. Returns App Store apps associated with a specific developer artist ID. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
appstore_developer accepts 3 parameters: lang, dev_id, country. Required: dev_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 appstore_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.
appstore_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 appstore_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 appstore_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.
appstore_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