input_tap

THE RISK

High Risk

Why input_tap needs a policy

This tool simulates a physical tap at given screen coordinates on an Android device. It triggers external operations (UI interactions) whose effects depend on arguments — tapping a coordinate could activate buttons, confirm dialogs, make purchases, or trigger other actions.

From the tool's definition 'Tap at specific coordinates' — triggers a UI input action on the Android device

Documented attack patterns abuse exactly the kind of access input_tap gives an agent:

POLICY

How to control input_tap

PolicyLayer is an MCP gateway — it sits between your AI agents and Android Debug Bridge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for input_tap:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "input_tap": {
      "limits": [
        {
          "counter": "input_tap_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Android Debug Bridge MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Android Debug Bridge MCP tools

Execute input_keyevent Send key events (BACK, HOME, ENTER, DELETE) Execute input_scroll Perform scroll action Execute input_text Input text into the current field Execute open_app Open an app using its package name and activity Write create_test_folder Create a test folder with the specified name Read capture_screenshot Capture a screenshot and save it to the test folder Read list_apps List installed apps matching a name pattern Read capture_ui_dump Capture UI hierarchy dump from the device

All 9 Android Debug Bridge MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Android Debug Bridge MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about input_tap

What does the input_tap tool do? +

Tap at specific coordinates. It is categorised as a Execute tool in the Android Debug Bridge MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on input_tap? +

Register the Android Debug Bridge MCP server in PolicyLayer and add a rule for input_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 Android Debug Bridge MCP. Nothing to install.

What risk level is input_tap? +

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

Can I rate-limit input_tap? +

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

Set action: deny in the PolicyLayer policy for input_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 input_tap? +

input_tap is provided by the Android Debug Bridge MCP server (tiagodanin/android-debug-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Android Debug Bridge MCP tool call.

Start from Android Debug Bridge MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →