AI agents call halt_release to permanently remove resources in Play Store — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'halt_release' strongly implies stopping or cancelling an active app release on the Google Play Store, which is likely irreversible or at minimum has significant operational impact. In context of a deployment server, halting a release could affect live app distribution to users.
From the tool's definition Tool name 'halt_release' on a server that manages app deployments and releases; description is empty.
Documented attack patterns abuse exactly the kind of access halt_release gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Play Store, and nothing reaches the server without passing your rules. This is the rule we recommend for halt_release:
{
"version": "1",
"default": "deny",
"hide": [
"halt_release"
]
}halt_release disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
halt_release. It is categorised as a Destructive tool in the Play Store MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Play Store MCP server in PolicyLayer and add a rule for halt_release: 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 Play Store. Nothing to install.
halt_release is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the halt_release 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 halt_release. 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.
halt_release is provided by the Play Store MCP server (lusky3/play-store-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Play Store, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Play Store tools catalogued and risk-classified — across an index of 43,000+ MCP servers.