// SCAN REPORT

Android Debug Bridge MCP

9 tools. 6 can modify or destroy data without limits.

6 write tools that can modify data. Rate limits recommended.

Last updated: 11 Jun 2026

6 can modify or destroy data

3 read-only

9 tools total

Community server · catalogue entry verified 11/06/2026

How to control Android Debug Bridge MCP ↓

TOOL MAP

What Android Debug Bridge MCP exposes to your agents

Read (3) Write / Execute (6) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Android Debug Bridge MCP tools

Execute · Medium input_keyevent This tool triggers external operations on an Android device by sending key events. Execute · Medium input_scroll This tool executes a scroll gesture on an Android device, which is an external operation that simulates user input. Execute · Medium input_tap This tool simulates a physical tap at given screen coordinates on an Android device. Execute · Medium input_text This tool executes an external operation (ADB text injection) on an Android device.

6 of Android Debug Bridge MCP's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Android Debug Bridge MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Android Debug Bridge MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "create_test_folder": {
    "limits": [
      {
        "counter": "create_test_folder_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "capture_screenshot": {
    "limits": [
      {
        "counter": "capture_screenshot_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Android Debug Bridge MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ANDROID DEBUG BRIDGE →

Free to start. No card required.

FULL CATALOGUE

All 9 Android Debug Bridge MCP tools

EXECUTE 5 tools

Execute input_keyevent Send key events (BACK, HOME, ENTER, DELETE) Execute input_scroll Perform scroll action Execute input_tap Tap at specific coordinates Execute input_text Input text into the current field Execute open_app Open an app using its package name and activity

WRITE 1 tools

Write create_test_folder Create a test folder with the specified name

READ 3 tools

Read capture_screenshot Capture a screenshot and save it to the test folder Read list_apps List installed apps matching a name pattern Read capture_ui_dump Capture UI hierarchy dump from the device

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Android Debug Bridge MCP

How do I prevent bulk modifications through Android Debug Bridge MCP? +

The Android Debug Bridge MCP server has 1 write tools including create_test_folder. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Android Debug Bridge MCP.

How many tools does the Android Debug Bridge MCP server expose? +

9 tools across 3 categories: Destructive, Read, Write. 3 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Android Debug Bridge MCP? +

Register the Android Debug Bridge MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Android Debug Bridge MCP tool call.

Deterministic rules across all 9 Android Debug Bridge MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ANDROID DEBUG BRIDGE →

Free to start. No card required.

9 Android Debug Bridge MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.