adb_wake · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_wake does on Openclaw Adb

AI agents invoke adb_wake to trigger actions in Openclaw Adb. 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 IT NEEDS A POLICY

Why adb_wake needs a policy

This tool sends an ADB command to wake the device screen, which is an external operation that affects the physical device state. It doesn't read data, write/modify stored data, delete anything, or involve finances. It falls under Execute as it triggers an external device operation. The blast radius is low since waking a screen is a minor, easily reversible action.

From the tool's definition 'Wake up the device screen' — triggers an external hardware/OS operation on a connected Android device via ADB

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_wake Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Openclaw Adb, so you can run agents against it safely.

FAQ

Questions about adb_wake

What does the adb_wake tool do? +

Wake up the device screen. It is categorised as a Execute tool in the Openclaw Adb 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_wake? +

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

What risk level is adb_wake? +

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

Can I rate-limit adb_wake? +

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

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

adb_wake is provided by the Openclaw Adb MCP server (wilsonbeam/openclaw-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.