# reboot_device

Reboot the device into specified mode.

Agent View of the PolicyLayer registry record for `reboot_device`. HTML page: https://policylayer.com/tools/0x-professor-droidforensics-suite/reboot-device

## Facts

- Tool: `reboot_device`
- Server: Android Forensics ADB MCP Server (`0x-professor/droidforensics-suite`) — https://policylayer.com/tools/0x-professor-droidforensics-suite.md
- Homepage: https://github.com/0x-Professor/DroidForensics-Suite
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "reboot_device",
    "arguments": {}
  }
}
```

## Why reboot_device is rated High

Rebooting a device is an external operation that interrupts running processes, can change boot modes (e.g., recovery, bootloader, fastboot), and may affect ongoing forensic acquisition. It is not a simple read or write, but an active command execution with significant operational impact.

From the tool's own definition: "'Reboot the device into specified mode' — triggers an external hardware operation (device reboot) that affects the target Android device's state"

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Android Forensics ADB MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reboot_device": {
      "limits": [
        {
          "counter": "reboot_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Android Forensics ADB MCP Server (57)

- `create_full_backup` — Destructive — https://policylayer.com/tools/0x-professor-droidforensics-suite/create-full-backup.md
- `adb_backup_device` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-backup-device.md
- `adb_connect_device` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-connect-device.md
- `adb_shell_command` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-shell-command.md
- `connect_to_device` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/connect-to-device.md
- `extract_with_root` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-with-root.md
- `generate_app_analysis_report` — Other — https://policylayer.com/tools/0x-professor-droidforensics-suite/generate-app-analysis-report.md
- `adb_devices` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-devices.md
- `adb_pull_data` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-pull-data.md
- `analyze_facebook_messenger` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-facebook-messenger.md
- `analyze_gmail` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-gmail.md
- `analyze_instagram` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-instagram.md
- `analyze_network_connections` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-network-connections.md
- `analyze_partition_info` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-partition-info.md
- `analyze_telegram` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-telegram.md
- `analyze_whatsapp` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-whatsapp.md
- `capture_dmesg` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/capture-dmesg.md
- `capture_logcat` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/capture-logcat.md
- `check_adb_status` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/check-adb-status.md
- `check_root_status` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/check-root-status.md
- `collect_common_artifacts` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/collect-common-artifacts.md
- `collect_forensic_artifacts` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/collect-forensic-artifacts.md
- `create_timeline` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/create-timeline.md
- `dump_database` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/dump-database.md
- `dump_system_settings` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/dump-system-settings.md
- `extract_app_credentials` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-app-credentials.md
- `extract_backup_to_tar` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-backup-to-tar.md
- `extract_exif_metadata` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-exif-metadata.md
- `extract_media_gallery_metadata` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-media-gallery-metadata.md
- `generate_executive_summary` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/generate-executive-summary.md
- …and 27 more: https://policylayer.com/tools/0x-professor-droidforensics-suite.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0x-professor-droidforensics-suite · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x-professor-droidforensics-suite