click_by_class · Android MCP Server MCP: Risk & Policy

WHAT IT DOES

What click_by_class does on Android MCP Server

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

This tool performs an interactive tap/click action on a live Android device UI, which constitutes executing an external operation. The effect depends entirely on what element is matched and tapped (could open apps, confirm dialogs, submit forms, etc.), making it Execute-level.

From the tool's definition Find element by class name and tap it — triggers a UI tap action on a matched element on the Android device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_by_class Rate-limited

click_by_class 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_class": {
      "limits": [
        {
          "counter": "click_by_class_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_class

What does the click_by_class tool do? +

Find element by class name and tap it. 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_class? +

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

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

Can I rate-limit click_by_class? +

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

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

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

// THE FULL RECORD

click_by_class is one line of Android MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →