adb_tap · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_tap does on Openclaw Adb

AI agents invoke adb_tap 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_tap needs a policy

This tool performs a UI interaction action (screen tap) on an Android device via ADB. It triggers an external operation on a real device whose effects depend on what is at the given coordinates — it could open apps, confirm dialogs, trigger purchases, etc. This is an Execute-category action with medium severity since the blast radius depends on context, but misuse could trigger unintended UI actions on the device.

From the tool's definition Tap on the screen at the specified coordinates

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_tap Rate-limited

adb_tap 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_tap": {
      "limits": [
        {
          "counter": "adb_tap_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_tap

What does the adb_tap tool do? +

Tap on the screen at the specified coordinates. 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_tap? +

Register the Openclaw Adb MCP server in PolicyLayer and add a rule for adb_tap: 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_tap? +

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

Can I rate-limit adb_tap? +

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

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

adb_tap 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.