Force-stop an app on the Android device.
AI agents invoke adb_stop_app to trigger actions in Claude Pascal MCP Server. 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.
This tool executes a command that immediately terminates a running application process on an Android device. While not destructive to data (the app's data persists), it is an active operation whose effects depend on which app is targeted as an argument. Force-stopping an app can disrupt user workflows, cause loss of unsaved data in that app, and potentially break dependent processes.
From the tool's definition Tool description: "Force-stop an app on the Android device." The verb "force-stop" indicates an active command that triggers an external operation on a connected Android device.
Documented attack patterns abuse exactly the kind of access adb_stop_app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_stop_app:
{
"version": "1",
"default": "deny",
"tools": {
"adb_stop_app": {
"limits": [
{
"counter": "adb_stop_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} adb_stop_app 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.
Free to start. No card required.
Force-stop an app on the Android device. It is categorised as a Execute tool in the Claude Pascal MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for adb_stop_app: 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 Pascal MCP Server. Nothing to install.
adb_stop_app 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 adb_stop_app 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 adb_stop_app. 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.
adb_stop_app is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Pascal MCP Server, 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.
53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.