reboot_device · Android Device MCP: Risk & Policy

WHAT IT DOES

What reboot_device does on Android Device

AI agents invoke reboot_device to trigger actions in Android Device. 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 in-the-moment action that terminates all running apps and services, causes downtime, and cannot be undone once initiated. While the device does come back online, the act of rebooting itself is a disruptive external operation rather than a data read/write.

From the tool's definition 'Reboot a specific Android device' — rebooting triggers an external hardware operation that interrupts all running processes and services on the device

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 Android Device, so you can run agents against it safely.

FAQ

Questions about reboot_device

What does the reboot_device tool do? +

Reboot a specific Android device using its serial number. It is categorised as a Execute tool in the Android Device 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 Android Device 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 Android Device. 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 Android Device MCP server (prashant1507/android-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.