store_upload

Upload APK/AAB to Google Play. Requires GOOGLE_PLAY_KEY_FILE env.

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-upload.md

WHAT IT DOES

What store_upload does on Claude Mobile

AI agents use store_upload 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_upload is rated Medium

This tool uploads app packages to Google Play Store, which is a write operation creating/publishing new content to an external platform. It is not directly financial but has high blast radius since publishing a malicious or incorrect app to Google Play could affect many users. It is reversible in the sense that apps can be unpublished, so Destructive is not the best fit. Write is the most appropriate category.

From the tool's definition Upload APK/AAB to Google Play

Attacks that exploit this kind of access

RECOMMENDED RULE

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

store_upload Rate-limited

store_upload 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_upload": {
      "limits": [
        {
          "counter": "store_upload_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_upload call is checked against it from then on.

FAQ

Questions about store_upload

What does the store_upload tool do? +

Upload APK/AAB to Google Play. Requires GOOGLE_PLAY_KEY_FILE env. 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_upload? +

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

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

Can I rate-limit store_upload? +

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

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

store_upload 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 →