adb_reboot

Reboot the device. Supports normal, recovery, and bootloader modes.

SERVERDeepadb SOURCEdeepadb

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-reboot.md

WHAT IT DOES

What adb_reboot does on Deepadb

AI agents invoke adb_reboot 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.

RISK

Why adb_reboot is rated High

Rebooting a device is an external operation that interrupts all running processes and can disrupt ongoing work. While it is technically reversible (the device comes back up), it triggers a significant side effect on the physical/virtual device. Booting into recovery or bootloader modes can further expose the device to potentially destructive operations, making this Execute at high severity.

From the tool's definition 'Reboot the device. Supports normal, recovery, and bootloader modes.'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_reboot 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_reboot, this is the rule to start with:

adb_reboot Rate-limited

adb_reboot 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_reboot": {
      "limits": [
        {
          "counter": "adb_reboot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_reboot call is checked against it from then on.

FAQ

Questions about adb_reboot

What does the adb_reboot tool do? +

Reboot the device. Supports normal, recovery, and bootloader modes. 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.

How do I enforce a policy on adb_reboot? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_reboot: 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.

What risk level is adb_reboot? +

adb_reboot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit adb_reboot? +

Yes. Add a rate_limit block to the adb_reboot 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.

How do I block adb_reboot completely? +

Set action: deny in the PolicyLayer policy for adb_reboot. 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.

What MCP server provides adb_reboot? +

adb_reboot 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.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →