adb_tap

Tap at x,y.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/adb-tap.md

WHAT IT DOES

What adb_tap does on LocalAnt

AI agents invoke adb_tap to trigger actions in LocalAnt. 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.

RISK

Why adb_tap is rated High

This tool executes a UI interaction (tap gesture) on an Android device at specified coordinates. It is an external operation that triggers device-side effects depending on what is at those coordinates. Effects are not inherently destructive or financial, but misuse could trigger unintended UI actions (e.g., confirming dialogs, initiating purchases), making it Execute with medium severity.

From the tool's definition 'Tap at x,y' — triggers a touch/tap input action on a connected Android device via ADB

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_tap safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_tap, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every adb_tap call is checked against it from then on.

FAQ

Questions about adb_tap

What does the adb_tap tool do? +

Tap at x,y. It is categorised as a Execute tool in the LocalAnt 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 LocalAnt 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 LocalAnt. 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 LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →