store_submit
Publish release draft to Google Play track
This record as markdown: /tools/alexgladkov-claude-in-mobile/store-submit.md
What store_submit does on Claude Mobile
AI agents use store_submit 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.
Why store_submit is rated Medium
This tool creates or modifies app releases on Google Play Store, which affects production mobile app distribution to end users. While not destructive (can be rolled back) or financial (no direct payment), it represents a significant Write action that alters publicly available software. The high severity reflects the broad impact on all app users if misused by an AI agent (e.g., publishing untested or malicious code).
From the tool's definition Tool name 'store_submit' and description 'Publish release draft to Google Play track' indicate creation/modification of published app releases in a public distribution channel.
Attacks that exploit this kind of access
The rule that runs store_submit 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_submit, this is the rule to start with:
store_submit 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every store_submit call is checked against it from then on.
Questions about store_submit
Publish release draft to Google Play track. 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.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for store_submit: 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.
store_submit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the store_submit 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 store_submit. 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.
store_submit 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.
More on Claude Mobile, and thousands of servers like it.
This server
Across the catalogue