adb_click · ADB MCP Server MCP: Risk & Policy

WHAT IT DOES

What adb_click does on ADB MCP Server

AI agents invoke adb_click 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_click needs a policy

This tool triggers a UI interaction (tap/click) on an Android device screen. It executes an action on an external device whose effects are entirely dependent on what is currently displayed and the coordinates provided. An AI agent could misuse this to confirm purchases, grant permissions, interact with sensitive UI elements, or perform unintended actions on the device.

From the tool's definition Click at specific coordinates on the device screen

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_click Rate-limited

adb_click 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_click": {
      "limits": [
        {
          "counter": "adb_click_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_click

What does the adb_click tool do? +

Click at specific coordinates on the device screen. 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_click? +

Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_click: 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_click? +

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

Can I rate-limit adb_click? +

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

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

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