android_uiautomator_click · Android MCP Server MCP

WHAT IT DOES

What android_uiautomator_click does on Android MCP Server

AI agents invoke android_uiautomator_click to trigger actions in Android 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 android_uiautomator_click needs a policy

This tool simulates user interaction by programmatically clicking UI elements on an Android device via UIAutomator. It triggers external operations on the device whose effects depend on which element is clicked — could dismiss dialogs, confirm purchases, grant permissions, or perform any in-app action.

From the tool's definition Click on a UI element by resource ID using UIAutomator

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_uiautomator_click Rate-limited

android_uiautomator_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": {
    "android_uiautomator_click": {
      "limits": [
        {
          "counter": "android_uiautomator_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 Android MCP Server, so you can run agents against it safely.

FAQ

Questions about android_uiautomator_click

What does the android_uiautomator_click tool do? +

Click on a UI element by resource ID using UIAutomator. It is categorised as a Execute tool in the Android 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 android_uiautomator_click? +

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

What risk level is android_uiautomator_click? +

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

Can I rate-limit android_uiautomator_click? +

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

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

android_uiautomator_click is provided by the Android MCP Server MCP server (jduartedj/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.