adb_stop_app_am
Force stops an Android app on the connected device using 'am force-stop'.
This record as markdown: /tools/ahmeth4n-renef-mcp/adb-stop-app-am.md
What adb_stop_app_am does on Renef
AI agents invoke adb_stop_app_am to trigger actions in Renef. 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 adb_stop_app_am is rated High
This tool executes a system command (Android Activity Manager's force-stop) that has observable side effects on the device state. While not destructive (the app isn't deleted), it actively terminates a running application process, which is an Execute operation.
From the tool's definition Tool uses 'am force-stop' to force stop an Android app, which is a command execution action that terminates a running process on the device. The description explicitly states it 'Force stops an Android app,' indicating active process termination.
Attacks that exploit this kind of access
The rule that runs adb_stop_app_am safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Renef, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_stop_app_am, this is the rule to start with:
adb_stop_app_am 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 Renef, apply this rule, and every adb_stop_app_am call is checked against it from then on.
Questions about adb_stop_app_am
Force stops an Android app on the connected device using 'am force-stop'. It is categorised as a Execute tool in the Renef MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Renef MCP server in PolicyLayer and add a rule for adb_stop_app_am: 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 Renef. Nothing to install.
adb_stop_app_am 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_am 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_am. 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_am is provided by the Renef MCP server (ahmeth4n/renef-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Renef, and thousands of servers like it.
This server
Across the catalogue