High Risk →

long_click

Perform a long click (press and hold) on a UI element. Useful for context menus, drag operations, or long press actions.

How to control long_click ↓

AI agents invoke long_click to trigger actions in MCP Android Agent. 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.

High Risk

This tool triggers UI interactions on an Android device, executing touch/press actions that can open context menus, initiate drags, or trigger long-press behaviors. The effects depend entirely on the target element and could cause unintended actions (e.g., deleting items via context menu, rearranging UI elements).

From the tool's definition 'Perform a long click (press and hold) on a UI element. Useful for context menus, drag operations, or long press actions.'

Documented attack patterns abuse exactly the kind of access long_click gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for long_click:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "long_click": {
      "limits": [
        {
          "counter": "long_click_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register MCP Android Agent — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the long_click tool do? +

Perform a long click (press and hold) on a UI element. Useful for context menus, drag operations, or long press actions. It is categorised as a Execute tool in the MCP Android Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on long_click? +

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

What risk level is long_click? +

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

Can I rate-limit long_click? +

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

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

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

Enforce policy on every MCP Android Agent tool call.

Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.