click_by_text · Android MCP Server MCP: Risk & Policy

WHAT IT DOES

What click_by_text does on Android MCP Server

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

This tool performs a browser/UI action by tapping a UI element on an Android device. It executes an interaction whose effect depends on what element is found and tapped (could open apps, confirm dialogs, submit forms, etc.). This is an Execute-category action with medium severity since misuse could trigger unintended UI actions but is limited by needing to match visible text.

From the tool's definition 'Find element by text and tap it' — triggers a UI interaction (tap) on an Android device element located by text content

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_by_text Rate-limited

click_by_text 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": {
    "click_by_text": {
      "limits": [
        {
          "counter": "click_by_text_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 click_by_text

What does the click_by_text tool do? +

Find element by text and tap it. More robust than manual tap_screen. 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 click_by_text? +

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

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

Can I rate-limit click_by_text? +

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

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

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