store_halt_rollout
Halt staged rollout on Google Play
This record as markdown: /tools/alexgladkov-claude-in-mobile/store-halt-rollout.md
What store_halt_rollout does on Claude Mobile
AI agents invoke store_halt_rollout to trigger actions in Claude Mobile. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why store_halt_rollout is rated High
This tool triggers an external operation on Google Play Store to halt a staged rollout of an app release. While it doesn't move money directly, it affects app distribution by stopping an in-progress rollout, which is a significant operational action with real-world consequences. It falls under Execute as it triggers an external platform operation.
From the tool's definition Halt staged rollout on Google Play
Attacks that exploit this kind of access
The rule that runs store_halt_rollout 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_halt_rollout, this is the rule to start with:
store_halt_rollout stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_halt_rollout call is checked against it from then on.
Questions about store_halt_rollout
Halt staged rollout on Google Play. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for store_halt_rollout: 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_halt_rollout is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the store_halt_rollout 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_halt_rollout. 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_halt_rollout 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