get_app_detail
Return one app's full record. Accepts the canonical id ("apple:284882215", "google:com.spotify.music"), a bare Apple track id, an Android package name, or a pasted App Store / Google Play URL. Cost: 1 credit.
This record as markdown: /tools/com-getappniche-mcp/get-app-detail.md
What get_app_detail does on Mcp
AI agents call get_app_detail to retrieve information from Mcp 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 |
|---|---|---|---|
app_id | string | Yes | The app to look up. Accepts the canonical '<store>:<store_id>' form ('apple:284882215', 'google:com.spotify.music'), a bare Apple track id ('284882215'), an And |
Parameters from the server's own tool schema.
Why get_app_detail is rated Low
This tool retrieves application metadata from public app stores (Apple App Store and Google Play). It performs a read-only query operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an attacker could enumerate app details but cannot alter app store data, execute code, or cause financial harm. Classification as Read is appropriate.
From the tool's definition Tool description states 'Return one app's full record' and accepts identifiers/URLs to retrieve data. No mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_app_detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_app_detail, this is the rule to start with:
get_app_detail 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 Mcp, apply this rule, and every get_app_detail call is checked against it from then on.
Questions about get_app_detail
Return one app's full record. Accepts the canonical id ("apple:284882215", "google:com.spotify.music"), a bare Apple track id, an Android package name, or a pasted App Store / Google Play URL. Cost: 1 credit. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_app_detail accepts 1 parameter: app_id. Required: app_id. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for get_app_detail: 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 Mcp. Nothing to install.
get_app_detail 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 get_app_detail 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 get_app_detail. 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.
get_app_detail is provided by the MCP server (@getappniche/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue