reboot_device · Enhanced ADB MCP Server MCP: Risk & Policy

WHAT IT DOES

What reboot_device does on Enhanced ADB MCP Server

AI agents invoke reboot_device to trigger actions in Enhanced 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.

WHY IT NEEDS A POLICY

Why reboot_device needs a policy

Rebooting a device is an irreversible system-level operation that terminates all running processes, interrupts active sessions, and can cause data loss for unsaved state. It is not a simple read or write, but an execution of a system command with broad impact. While the device does come back online, the act itself is disruptive and cannot be undone in the moment.

From the tool's definition 'Reboot the device' — triggers a full device restart, an external system operation with significant side effects

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reboot_device Rate-limited

reboot_device 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": {
    "reboot_device": {
      "limits": [
        {
          "counter": "reboot_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Enhanced ADB MCP Server, so you can run agents against it safely.

FAQ

Questions about reboot_device

What does the reboot_device tool do? +

Reboot the device. It is categorised as a Execute tool in the Enhanced ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reboot_device? +

Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for reboot_device: 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 Enhanced ADB MCP Server. Nothing to install.

What risk level is reboot_device? +

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

Can I rate-limit reboot_device? +

Yes. Add a rate_limit block to the reboot_device 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 reboot_device completely? +

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

reboot_device is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.