click_point · Android MCP Server MCP: Risk & Policy

WHAT IT DOES

What click_point does on Android MCP Server

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

Clicking at arbitrary coordinates on an Android device can trigger any UI action, including confirming purchases, granting permissions, installing apps, or activating destructive controls. The effect depends entirely on what is displayed at those coordinates at runtime, making this an Execute-category tool with high blast radius if misused by an AI agent.

From the tool's definition Click at a specific X, Y coordinate — triggers a UI interaction on an Android device at arbitrary screen coordinates

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_point Rate-limited

click_point 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_point": {
      "limits": [
        {
          "counter": "click_point_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_point

What does the click_point tool do? +

Click at a specific X, Y coordinate. 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_point? +

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

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

Can I rate-limit click_point? +

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

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

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