adb_press_key · ADB MCP Server MCP: Risk & Policy

WHAT IT DOES

What adb_press_key does on ADB MCP Server

AI agents invoke adb_press_key to trigger actions in ADB MCP Server. 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_key needs a policy

Pressing a key is an external operation executed on a device that can trigger arbitrary actions depending on the key pressed (e.g., HOME, BACK, POWER, volume keys, or even triggering app actions). It is not a read, it modifies device state transiently, and while reversible in many cases, it can trigger irreversible actions (e.g., confirming a delete dialog).

From the tool's definition 'Press a key on the device' — triggers an input/keypress action on a remote Android device via ADB

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_press_key Rate-limited

adb_press_key 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_key": {
      "limits": [
        {
          "counter": "adb_press_key_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 ADB MCP Server, so you can run agents against it safely.

FAQ

Questions about adb_press_key

What does the adb_press_key tool do? +

Press a key on the device. It is categorised as a Execute tool in the ADB MCP Server 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_key? +

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

What risk level is adb_press_key? +

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

Can I rate-limit adb_press_key? +

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

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

adb_press_key is provided by the ADB MCP Server MCP server (richard0913/adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.