adb_qemu_stop

What adb_qemu_stop does on Deepadb

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

Why adb_qemu_stop is rated High

This tool triggers an external operation (stopping a QEMU VM process) whose effects depend on which VM is targeted. While not destructive to data itself (VMs can be restarted), it is an Execute-class action because it triggers a system-level operation with immediate side effects. Severity is high because an AI agent could halt critical virtual environments, causing service disruption or loss of work in progress.

From the tool's definition Tool description states it 'Stop[s] a running QEMU virtual machine' and 'Sends SIGTERM for graceful shutdown, with force kill option.' This performs a direct external operation (process termination) with immediate effects.

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

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

Questions about adb_qemu_stop