store_promote

Promote release between Google Play tracks

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What store_promote does on Claude Mobile

AI agents use store_promote to create or update resources in Claude Mobile, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Mobile environment.

RISK

Why store_promote is rated Medium

This tool modifies app release configuration on Google Play by promoting versions between tracks (e.g., internal→alpha→beta→production), affecting what versions are visible and available to users.

From the tool's definition Tool name 'store_promote' and description 'Promote release between Google Play tracks' indicates modifying app distribution state on Google Play Store, which creates or alters release metadata and availability across different distribution channels (tracks).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

store_promote Rate-limited

store_promote stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "store_promote": {
      "limits": [
        {
          "counter": "store_promote_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_promote call is checked against it from then on.

FAQ

Questions about store_promote

What does the store_promote tool do? +

Promote release between Google Play tracks. It is categorised as a Write tool in the Claude Mobile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on store_promote? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for store_promote: 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_promote? +

store_promote is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit store_promote? +

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

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

store_promote 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →