adb_emulator_start

Launch an Android Virtual Device (AVD) emulator. Returns once the emulator process has started.

SERVERDeepadb SOURCEdeepadb

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-emulator-start.md

WHAT IT DOES

What adb_emulator_start does on Deepadb

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

RISK

Why adb_emulator_start is rated High

This tool triggers execution of an Android emulator process, which is an external operation whose side effects (resource consumption, emulator state, network interfaces, etc.) depend on emulator configuration and system state. The blast radius is high because an uncontrolled emulator launch could exhaust system resources, create security boundaries, or enable further attacks on the emulated Android system.

From the tool's definition Tool name 'adb_emulator_start' and description 'Launch an Android Virtual Device (AVD) emulator' indicate the tool starts/launches an external process or service.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adb_emulator_start Rate-limited

adb_emulator_start 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": {
    "adb_emulator_start": {
      "limits": [
        {
          "counter": "adb_emulator_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_emulator_start call is checked against it from then on.

FAQ

Questions about adb_emulator_start

What does the adb_emulator_start tool do? +

Launch an Android Virtual Device (AVD) emulator. Returns once the emulator process has started. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on adb_emulator_start? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_emulator_start: 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 Deepadb. Nothing to install.

What risk level is adb_emulator_start? +

adb_emulator_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit adb_emulator_start? +

Yes. Add a rate_limit block to the adb_emulator_start 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 adb_emulator_start completely? +

Set action: deny in the PolicyLayer policy for adb_emulator_start. 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 adb_emulator_start? +

adb_emulator_start is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →adb_backup_device on Android Forensics ADB MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →