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

Agent View of the PolicyLayer registry record for `get_app_detail`. HTML page: https://policylayer.com/tools/com-getappniche-mcp/get-app-detail

## Facts

- Tool: `get_app_detail`
- Server: Mcp (`@getappniche/mcp`) — https://policylayer.com/tools/com-getappniche-mcp.md
- Install: `npx -y @getappniche/mcp`
- Homepage: https://github.com/getappniche/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

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

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_app_detail",
    "arguments": {
      "app_id": "<app_id>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_app_detail": {}
  }
}
```

## Other tools on Mcp (6)

- `batch_keyword_difficulty` — Read — https://policylayer.com/tools/com-getappniche-mcp/batch-keyword-difficulty.md
- `get_app_historicals` — Read — https://policylayer.com/tools/com-getappniche-mcp/get-app-historicals.md
- `get_app_reviews` — Read — https://policylayer.com/tools/com-getappniche-mcp/get-app-reviews.md
- `get_keyword_difficulty` — Read — https://policylayer.com/tools/com-getappniche-mcp/get-keyword-difficulty.md
- `get_supported_countries` — Read — https://policylayer.com/tools/com-getappniche-mcp/get-supported-countries.md
- `search_apps` — Read — https://policylayer.com/tools/com-getappniche-mcp/search-apps.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-getappniche-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getappniche-mcp