Get version history for an App Store app. Returns an array of versions with:\n
AI agents call app-store-version-history to retrieve information from App Market Intelligence MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical version information about an App Store app. It performs a read-only query operation that returns data without creating, modifying, deleting, or executing any code. There are no destructive, financial, or execution risks. The blast radius of misuse is minimal as it only exposes publicly available version history metadata.
From the tool's definition Tool name 'app-store-version-history' and description 'Get version history for an App Store app. Returns an array of versions' indicate data retrieval without modification or side effects.
Documented attack patterns abuse exactly the kind of access app-store-version-history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and App Market Intelligence MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for app-store-version-history:
{
"version": "1",
"default": "deny",
"tools": {
"app-store-version-history": {}
}
} app-store-version-history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get version history for an App Store app. Returns an array of versions with:\n. It is categorised as a Read tool in the App Market Intelligence MCP MCP Server, which means it retrieves data without modifying state.
Register the App Market Intelligence MCP server in PolicyLayer and add a rule for app-store-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 App Market Intelligence MCP. Nothing to install.
app-store-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 app-store-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 app-store-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.
app-store-version-history is provided by the App Market Intelligence MCP server (jiantaofu/appinsightmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from App Market Intelligence MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 App Market Intelligence MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.