New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

store_submit

Publish release draft to Google Play track

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

Questions about store_submit

What does the store_submit tool do? +

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.

How do I enforce a policy on store_submit? +

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.

What risk level is store_submit? +

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

Can I rate-limit store_submit? +

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.

How do I block store_submit completely? +

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.

What MCP server provides store_submit? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Mobile's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.