adb_restart_app
Force-stop then re-launch an app. The most frequent debugging workflow in a single call.
This record as markdown: /tools/io-github-fullread-deepadb/adb-restart-app.md
What adb_restart_app does on Deepadb
AI agents invoke adb_restart_app 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_restart_app is rated High
This tool executes commands that control application lifecycle on a connected Android device via ADB. While not destructive (the app remains on the device), it actively triggers external operations (force-stop and relaunch) whose side effects are significant: it can interrupt user workflows, lose unsaved data in the target app, and affect system state.
From the tool's definition Tool performs force-stop (system-level termination) and re-launch operations on applications. These are external operations whose effects depend on which app is targeted.
Attacks that exploit this kind of access
The rule that runs adb_restart_app 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_restart_app, this is the rule to start with:
adb_restart_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_restart_app call is checked against it from then on.
Questions about adb_restart_app
Force-stop then re-launch an app. The most frequent debugging workflow in a single call. 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_restart_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 Deepadb. Nothing to install.
adb_restart_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_restart_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_restart_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_restart_app 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