adb_press_home · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_press_home does on Openclaw Adb

AI agents invoke adb_press_home 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_press_home needs a policy

This tool executes an external operation on an Android device by simulating a home button press. It does not read data, write/create data persistently, delete anything, or involve finances. It is a device control action that navigates the UI state, fitting the Execute category. Severity is low because pressing home is a benign navigation action with minimal blast radius.

From the tool's definition Press the home button — triggers a physical device action via ADB (Android Debug Bridge), simulating a hardware button press on the connected Android device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_press_home Rate-limited

adb_press_home 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_press_home": {
      "limits": [
        {
          "counter": "adb_press_home_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_press_home

What does the adb_press_home tool do? +

Press the home button. 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_press_home? +

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

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

Can I rate-limit adb_press_home? +

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

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

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