appstore_version_history
Retrieve App Store version history. Returns the version history entries shown in the App Store "What's New" section.
This record as markdown: /tools/crawlora-mcp/appstore-version-history.md
What appstore_version_history does on Crawlora
AI agents call appstore_version_history 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 | App Store numeric track ID (digits only) |
lang | string | — | Result language tag |
country | string | — | Two-letter storefront country code |
Parameters from the server's own tool schema.
Why appstore_version_history is rated Low
This tool queries publicly available version history information from the App Store and returns it without modifying, deleting, or executing any operations. It is a pure data retrieval operation with no blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Retrieve App Store version history' and 'Returns the version history entries shown in the App Store'. The verb 'Retrieve' and 'Returns' indicate a query/fetch operation with no side effects.
Attacks that exploit this kind of access
The rule that runs appstore_version_history 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_version_history, this is the rule to start with:
appstore_version_history 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_version_history call is checked against it from then on.
Questions about appstore_version_history
Retrieve App Store version history. Returns the version history entries shown in the App Store "What's New" section. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
appstore_version_history 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 appstore_version_history: 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_version_history 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_version_history 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_version_history. 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_version_history 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