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

store_halt_rollout

Halt staged rollout on Google Play

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile
High RISK CLASS
Category Execute
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-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

Questions about store_halt_rollout

What does the store_halt_rollout tool do? +

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.

How do I enforce a policy on store_halt_rollout? +

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.

What risk level is store_halt_rollout? +

store_halt_rollout is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit store_halt_rollout? +

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.

How do I block store_halt_rollout completely? +

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.

What MCP server provides store_halt_rollout? +

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.

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