# emu_reboot

Power-cycle the console, optionally inserting another disc (project name or ISO).

Agent View of the PolicyLayer registry record for `emu_reboot`. HTML page: https://policylayer.com/tools/3do-dev/emu-reboot

## Facts

- Tool: `emu_reboot`
- Server: 3do Dev (`geekychris/3do-dev`) — https://policylayer.com/tools/3do-dev.md
- Homepage: https://github.com/geekychris/3do-dev
- 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": "emu_reboot",
    "arguments": {}
  }
}
```

## Why emu_reboot is rated High

Triggers external emulator operation with side effects dependent on provided disc argument.

From the tool's own definition: "Power-cycle console, optionally inserting disc"

## Use case

AI agents invoke emu_reboot to trigger actions in 3do Dev. 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 3do Dev:

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

## Other tools on 3do Dev (47)

- `build` — Execute — https://policylayer.com/tools/3do-dev/build.md
- `emu_attach` — Execute — https://policylayer.com/tools/3do-dev/emu-attach.md
- `emu_boot` — Execute — https://policylayer.com/tools/3do-dev/emu-boot.md
- `emu_break` — Execute — https://policylayer.com/tools/3do-dev/emu-break.md
- `emu_cmd` — Execute — https://policylayer.com/tools/3do-dev/emu-cmd.md
- `emu_continue` — Execute — https://policylayer.com/tools/3do-dev/emu-continue.md
- `emu_halt` — Execute — https://policylayer.com/tools/3do-dev/emu-halt.md
- `emu_hold` — Execute — https://policylayer.com/tools/3do-dev/emu-hold.md
- `emu_input` — Execute — https://policylayer.com/tools/3do-dev/emu-input.md
- `emu_look` — Execute — https://policylayer.com/tools/3do-dev/emu-look.md
- `emu_pause` — Execute — https://policylayer.com/tools/3do-dev/emu-pause.md
- `emu_press` — Execute — https://policylayer.com/tools/3do-dev/emu-press.md
- `emu_record_gif` — Execute — https://policylayer.com/tools/3do-dev/emu-record-gif.md
- `emu_regs` — Execute — https://policylayer.com/tools/3do-dev/emu-regs.md
- `emu_reset` — Execute — https://policylayer.com/tools/3do-dev/emu-reset.md
- `emu_restart` — Execute — https://policylayer.com/tools/3do-dev/emu-restart.md
- `emu_run` — Execute — https://policylayer.com/tools/3do-dev/emu-run.md
- `emu_run_until` — Execute — https://policylayer.com/tools/3do-dev/emu-run-until.md
- `emu_sequence` — Execute — https://policylayer.com/tools/3do-dev/emu-sequence.md
- `emu_step` — Execute — https://policylayer.com/tools/3do-dev/emu-step.md
- `emu_stepi` — Execute — https://policylayer.com/tools/3do-dev/emu-stepi.md
- `emu_stop` — Execute — https://policylayer.com/tools/3do-dev/emu-stop.md
- `emu_trace` — Execute — https://policylayer.com/tools/3do-dev/emu-trace.md
- `emu_watch` — Execute — https://policylayer.com/tools/3do-dev/emu-watch.md
- `emu_write_mem` — Execute — https://policylayer.com/tools/3do-dev/emu-write-mem.md
- `gdb_run` — Execute — https://policylayer.com/tools/3do-dev/gdb-run.md
- `run_tests` — Execute — https://policylayer.com/tools/3do-dev/run-tests.md
- `emu_crashes` — Read — https://policylayer.com/tools/3do-dev/emu-crashes.md
- `emu_disasm` — Read — https://policylayer.com/tools/3do-dev/emu-disasm.md
- `emu_log` — Read — https://policylayer.com/tools/3do-dev/emu-log.md
- …and 17 more: https://policylayer.com/tools/3do-dev.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=3do-dev · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/3do-dev
