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).

SERVERCrawlora SOURCEcrawlora-mcp

Low RISK CLASS

Category Read

Parameters 50 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/appstore-app.md

WHAT IT DOES

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.

RISK

Why appstore_app is rated Low

Even though appstore_app only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

appstore_app is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "appstore_app": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about appstore_app

What does the appstore_app tool do? +

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.

What parameters does appstore_app accept? +

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.

How do I enforce a policy on appstore_app? +

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.

What risk level is appstore_app? +

appstore_app is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit appstore_app? +

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.

How do I block appstore_app completely? +

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.

What MCP server provides appstore_app? +

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.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →