[Google Play] Get detailed information about an app
AI agents call gp_app to retrieve information from Store Scraper MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool that queries the Google Play Store API to fetch app metadata (details, ratings, reviews, etc.). There are no side effects, no data modification, no code execution, and no financial implications. The worst-case misuse (e.g., automated mass scraping) would be a technical/policy violation rather than a security risk to data integrity or availability.
From the tool's definition Tool retrieves 'detailed information about an app' from Google Play Store. The verb 'Get' and the function 'gp_app' indicate a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
[Google Play] Get detailed information about an app. It is categorised as a Read tool in the Store Scraper MCP MCP Server, which means it retrieves data without modifying state.
Register the Store Scraper MCP server in PolicyLayer and add a rule for gp_app: 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 Store Scraper MCP. Nothing to install.
gp_app 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 gp_app 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 gp_app. 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.
gp_app is provided by the Store Scraper MCP server (miguelalvred/mobile-store-scraper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →