# get_app_historicals

Return historical metric points for one app (daily up to 90 days, weekly beyond). Cost: 1 credit.

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

## Facts

- Tool: `get_app_historicals`
- 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: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `days` | integer | no | Length of the history window in days, 7-730 (default 30). Points are daily up to 90 days and weekly beyond that. |
| `store` | string | no | Which store the store_id belongs to: 'apple' or 'google'. |
| `store_id` | string | yes | Store-native app id without the store prefix: numeric track id for Apple ('284882215'), bundle id for Google ('com.spotify.music'). |

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_historicals",
    "arguments": {
      "store_id": "<store_id>"
    }
  }
}
```

## Why get_app_historicals is rated Low

This tool retrieves historical metrics (likely app store rankings, download counts, ratings, etc.) for analysis and discovery purposes. There are no side effects, data modifications, code execution, deletions, or financial transactions. It is a passive data lookup aligned with the server's stated purpose of providing 'app discovery, ASO keywords, reviews' information to AI agents.

From the tool's own definition: "Tool name 'get_app_historicals' and description 'Return historical metric points for one app' indicate data retrieval with no modification capability."

## Use case

AI agents call get_app_historicals 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_historicals": {}
  }
}
```

## Other tools on Mcp (6)

- `batch_keyword_difficulty` — Read — https://policylayer.com/tools/com-getappniche-mcp/batch-keyword-difficulty.md
- `get_app_detail` — Read — https://policylayer.com/tools/com-getappniche-mcp/get-app-detail.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