get_app_reviews

SERVERMcp SOURCE@getappniche/mcp

Low RISK CLASS

Category Read

Parameters 90 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-getappniche-mcp/get-app-reviews.md

WHAT IT DOES

What get_app_reviews does on Mcp

AI agents call get_app_reviews 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
`limit`	integer	—	How many reviews to return, 1-50 (default 10).
`store`	object	—	Filter to reviews from one store: 'apple' or 'google'.
`topic`	object	—	Filter by an extracted topic label, e.g. 'pricing', 'onboarding', 'bugs'.
`app_id`	object	—	Any app to read reviews for, whether or not the workspace tracks it. Accepts 'apple:284882215', 'google:com.duolingo', a bare Apple track id, an Android package
`offset`	integer	—	How many reviews to skip before returning results. Live store reads ('app_id' set) reach the 200 newest reviews per app and storefront, so page until 'has_more'
`country`	string	—	Two-letter storefront code the reviews are read from, e.g. 'US', 'DE' (default 'US'). Only applies when 'app_id' is used. For Google Play this also picks the re
`store_id`	object	—	Filter to one app by its store-native id, e.g. '284882215' or 'com.spotify.music'.
`sentiment`	object	—	Filter by review sentiment: 'positive', 'neutral' or 'negative'.
`tracked_app_id`	object	—	UUID of one tracked app in the caller's workspace. Omit to read reviews across all tracked apps.

Parameters from the server's own tool schema.

RISK

Why get_app_reviews is rated Low

This tool retrieves and queries existing app review data from public storefronts or internal workspace tracking. It has no side effects—it neither modifies, deletes, executes code, nor commits financial transactions. The cost mechanism (1 credit) is metering/billing, not a financial transaction itself. Classification as Read is appropriate for data retrieval operations.

From the tool's definition Tool description explicitly states 'Read app reviews' and retrieves data from app stores (App Store or Google Play) or workspace tracked apps with sentiment/topics analysis.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_app_reviews 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_reviews, this is the rule to start with:

get_app_reviews Allowed

get_app_reviews 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": {
    "get_app_reviews": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every get_app_reviews call is checked against it from then on.

FAQ

Questions about get_app_reviews

What does the get_app_reviews tool do? +

Read app reviews two ways: pass app_id for live store reviews of ANY app — App Store or Google Play — (no tracking needed, storefront selectable), or omit it to read the workspace's tracked apps with sentiment, topics and improvement areas attached. Live Google Play rows carry no title (Play reviews have none). Cost: 1 credit. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_app_reviews accept? +

get_app_reviews accepts 9 parameters: limit, store, topic, app_id, offset, country, store_id, sentiment, tracked_app_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_app_reviews? +

Register the MCP server in PolicyLayer and add a rule for get_app_reviews: 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.

What risk level is get_app_reviews? +

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

Can I rate-limit get_app_reviews? +

Yes. Add a rate_limit block to the get_app_reviews 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 get_app_reviews completely? +

Set action: deny in the PolicyLayer policy for get_app_reviews. 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 get_app_reviews? +

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

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 7 tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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