adb_emulator_stop

What adb_emulator_stop does on Deepadb

AI agents invoke adb_emulator_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_emulator_stop is rated High

This tool triggers termination of an external process (the Android emulator), which is an Execute category action. While not destructive to persistent data, stopping an emulator unexpectedly could interrupt workflows, lose in-memory state, or disrupt dependent operations. The severity is high because an AI agent misusing this could terminate critical emulation environments without warning or consent.

From the tool's definition adb_emulator_stop is an action verb that stops (terminates) a running emulator process. The description 'Stop a running emulator' indicates an external operation with observable side effects.

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

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

Questions about adb_emulator_stop