AI agents call get_releases to retrieve information from Play Store without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries release status information from the Google Play Developer API. It performs a read-only operation that returns data about existing releases without creating, modifying, deleting, or executing anything. No state changes or destructive actions are possible. Severity is low because the worst misuse would be information disclosure of publicly or internally available release metadata.
From the tool's definition Tool name is 'get_releases' and description states 'Get release status for all tracks of an app' — uses 'Get' verb indicating retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_releases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Play Store, and nothing reaches the server without passing your rules. This is the rule we recommend for get_releases:
{
"version": "1",
"default": "deny",
"tools": {
"get_releases": {}
}
}get_releases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get release status for all tracks of an app. It is categorised as a Read tool in the Play Store MCP Server, which means it retrieves data without modifying state.
Register the Play Store MCP server in PolicyLayer and add a rule for get_releases: 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 Play Store. Nothing to install.
get_releases 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_releases 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_releases. 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_releases is provided by the Play Store MCP server (lusky3/play-store-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Play Store, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Play Store tools catalogued and risk-classified — across an index of 43,000+ MCP servers.