// SCAN REPORT

Openclaw Adb

30 tools. 22 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

22 can modify or destroy data

8 read-only

30 tools total

Community server · catalogue entry verified 30/06/2026

How to control Openclaw Adb ↓

TOOL MAP

What Openclaw Adb exposes to your agents

Read (8) Write / Execute (20) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Openclaw Adb tools

Destructive · High adb_clear_data This tool permanently erases application data without possibility of recovery. Destructive · High adb_uninstall_app Uninstalling an application is a destructive operation that cannot be easily undone and results in permanent removal of the app and associated data. Execute · High adb_force_stop Force-stopping an application is an external execution action that immediately kills a running process on a connected Android device. Execute · Critical adb_shell This tool permits arbitrary shell command execution on a connected Android device.

22 of Openclaw Adb's 30 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Openclaw Adb

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

Deny destructive operations

{
  "adb_clear_data": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "adb_push_file": {
    "limits": [
      {
        "counter": "adb_push_file_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "adb_call_state": {
    "limits": [
      {
        "counter": "adb_call_state_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 Openclaw Adb — 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 OPENCLAW ADB →

Instant setup, no code required.

FULL CATALOGUE

All 30 Openclaw Adb tools

DESTRUCTIVE 2 tools

Destructive adb_clear_data Clear all data for an application Destructive adb_uninstall_app Uninstall an app from the device

EXECUTE 18 tools

Execute adb_answer_call Answer an incoming call Execute adb_dial_number Open the dialer with a number (does not dial - user must press call) Execute adb_end_call End the current phone call Execute adb_force_stop Force stop an application Execute adb_install_app Install an APK file on the device Execute adb_lock Lock the device screen Execute adb_long_press Long press on the screen at the specified coordinates Execute adb_make_call Make a phone call to the specified number (dials immediately) Execute adb_press_back Press the back button Execute adb_press_home Press the home button Execute adb_press_key Press a key on the device (using Android keycode) Execute adb_shell Execute a shell command on the Android device Execute adb_start_activity Start an activity with the given intent Execute adb_swipe Swipe from one point to another on the screen Execute adb_tap Tap on the screen at the specified coordinates Execute adb_type_text Type text into the currently focused input field Execute adb_unlock Unlock the device with password, PIN, pattern, or swipe. Pattern uses 3x3 grid numbered 0-8 (top-left to botto Execute adb_wake Wake up the device screen

WRITE 2 tools

Write adb_push_file Push a file from local machine to the Android device Write adb_send_sms Open SMS composer with a pre-filled message (user must press send)

READ 8 tools

Read adb_call_state Get the current call state (idle, ringing, or offhook) Read adb_device_info Get detailed information about an Android device (model, brand, Android version, etc.) Read adb_is_locked Check if the device screen is locked Read adb_list_devices List all connected Android devices with their status and info Read adb_list_packages List installed packages on the device Read adb_pull_file Pull a file from the Android device to local machine Read adb_screen_size Get the screen dimensions of the device Read adb_screenshot Take a screenshot of the device screen and return as base64 PNG

EXPLORE

Related servers

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

FAQ

Questions about Openclaw Adb

Can an AI agent delete data through the Openclaw Adb MCP server? +

Yes. The Openclaw Adb server exposes 2 destructive tools including adb_clear_data, adb_uninstall_app. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Openclaw Adb? +

The Openclaw Adb server has 2 write tools including adb_push_file, adb_send_sms. 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 Openclaw Adb.

How many tools does the Openclaw Adb MCP server expose? +

30 tools across 4 categories: Destructive, Execute, Read, Write. 8 are read-only. 22 can modify, create, or delete data.

How do I enforce a policy on Openclaw Adb? +

Register the Openclaw Adb 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 Openclaw Adb tool call.

Deterministic rules across all 30 Openclaw Adb tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON OPENCLAW ADB →

Instant setup, no code required.

30 Openclaw Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.