Force-stop an app by package name.
AI agents invoke adb_app_stop to trigger actions in ADB 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 triggers an external operation (process termination on a controlled Android device) whose effects depend on the package name argument supplied by the agent. Force-stopping an app is not reversible in the sense that it causes immediate interruption of running code and state loss. It exceeds Write (which is reversible modification) but does not meet Destructive criteria (data is not deleted/overwritten).
From the tool's definition Tool name 'adb_app_stop' combined with description 'Force-stop an app by package name' indicates termination of a running process on an Android device.
Attacks that exploit this kind of access
Force-stop an app by package name. It is categorised as a Execute tool in the ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_app_stop: 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 ADB MCP Server. Nothing to install.
adb_app_stop 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_app_stop 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_app_stop. 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_app_stop is provided by the ADB MCP Server MCP server (lll-404/adb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →