get_app_historicals
Return historical metric points for one app (daily up to 90 days, weekly beyond). Cost: 1 credit.
This record as markdown: /tools/com-getappniche-mcp/get-app-historicals.md
What get_app_historicals does on Mcp
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | Length of the history window in days, 7-730 (default 30). Points are daily up to 90 days and weekly beyond that. |
store | string | — | 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.
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 definition Tool name 'get_app_historicals' and description 'Return historical metric points for one app' indicate data retrieval with no modification capability.
Attacks that exploit this kind of access
The rule that runs get_app_historicals 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_historicals, this is the rule to start with:
get_app_historicals 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_historicals call is checked against it from then on.
Questions about get_app_historicals
Return historical metric points for one app (daily up to 90 days, weekly beyond). 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_historicals accepts 3 parameters: days, store, store_id. Required: store_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_historicals: 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_historicals 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_historicals 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_historicals. 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_historicals 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