android_tap · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What android_tap does on DevLab MCP Suite

AI agents invoke android_tap to trigger actions in DevLab MCP Suite. 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 android_tap needs a policy

This tool executes an adb shell command that triggers a UI interaction (tap) on an Android device. The effect depends on the coordinates provided and whatever UI element resides there — it could trigger any action including confirmations, deletions, or purchases.

From the tool's definition 'Run adb shell input tap with x/y coordinates' — directly executes an adb shell command to simulate a tap on the device screen

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_tap Rate-limited

android_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": {
    "android_tap": {
      "limits": [
        {
          "counter": "android_tap_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 DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about android_tap

What does the android_tap tool do? +

Run adb shell input tap with x/y coordinates. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on android_tap? +

Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_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 DevLab MCP Suite. Nothing to install.

What risk level is android_tap? +

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

Can I rate-limit android_tap? +

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

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

android_tap is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.