adb_force_stop
Force-stop an app immediately. The most common debugging action.
This record as markdown: /tools/io-github-fullread-deepadb/adb-force-stop.md
What adb_force_stop does on Deepadb
AI agents invoke adb_force_stop to trigger actions in Deepadb. 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_force_stop is rated High
Force-stopping an app is an execution action that kills a running process. It is reversible (the app can be restarted), so it doesn't qualify as Destructive, but it does trigger an external operation (process termination on the Android device) whose effect depends on the argument (which app to stop). Misuse could disrupt critical apps (e.g., stopping a security or system app), hence medium severity.
From the tool's definition "Force-stop an app immediately" — terminates a running application process on the device
Attacks that exploit this kind of access
The rule that runs adb_force_stop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_force_stop, this is the rule to start with:
adb_force_stop 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 Deepadb, apply this rule, and every adb_force_stop call is checked against it from then on.
Questions about adb_force_stop
Force-stop an app immediately. The most common debugging action. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_force_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 Deepadb. Nothing to install.
adb_force_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_force_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_force_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_force_stop is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue