store_get_releases

Get current releases across Google Play tracks

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/store-get-releases.md

WHAT IT DOES

What store_get_releases does on Claude Mobile

AI agents call store_get_releases to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why store_get_releases is rated Low

This tool retrieves publicly available release information from Google Play Store without creating, modifying, deleting, or executing any operations. It performs a read-only query operation that returns existing data about app releases. The blast radius of misuse is minimal—an agent could only retrieve information that is already public.

From the tool's definition Tool name 'store_get_releases' and description 'Get current releases across Google Play tracks' indicate a query/retrieval operation with no modification of data or external state changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs store_get_releases safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store_get_releases, this is the rule to start with:

store_get_releases Allowed

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

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

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

FAQ

Questions about store_get_releases

What does the store_get_releases tool do? +

Get current releases across Google Play tracks. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on store_get_releases? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for store_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 Claude Mobile. Nothing to install.

What risk level is store_get_releases? +

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

Can I rate-limit store_get_releases? +

Yes. Add a rate_limit block to the store_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.

How do I block store_get_releases completely? +

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

What MCP server provides store_get_releases? +

store_get_releases is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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