appstore_app
Retrieve full App Store app details. Returns normalized app metadata from the App Store lookup API. Provide either id (numeric track ID) or app_id (bundle ID).
This record as markdown: /tools/crawlora-mcp/appstore-app.md
What appstore_app does on Crawlora
AI agents call appstore_app 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 | — | App Store numeric track ID (digits only) |
lang | string | — | Result language tag |
app_id | string | — | App Store bundle ID |
country | string | — | Two-letter storefront country code |
ratings | boolean | — | Include ratings histogram |
Parameters from the server's own tool schema.
Why appstore_app is rated Low
This tool performs a straightforward query operation against the App Store API to fetch publicly available app metadata. It accepts input parameters (app ID or bundle ID) and returns information without side effects. There is no capability to modify, execute code, delete data, or commit financial transactions.
From the tool's definition Tool description explicitly states 'Retrieve full App Store app details' and 'Returns normalized app metadata from the App Store lookup API'.
Attacks that exploit this kind of access
The rule that runs appstore_app 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_app, this is the rule to start with:
appstore_app 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_app call is checked against it from then on.
Questions about appstore_app
Retrieve full App Store app details. Returns normalized app metadata from the App Store lookup API. Provide either id (numeric track ID) or app_id (bundle ID). It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
appstore_app accepts 5 parameters: id, lang, app_id, country, ratings. 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_app: 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_app 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_app 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_app. 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_app 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