ui_tap_text

Tap element by text via Accessibility API (Desktop/macOS only)

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/ui-tap-text.md

WHAT IT DOES

What ui_tap_text does on Claude Mobile

AI agents invoke ui_tap_text to trigger actions in Claude Mobile. 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.

RISK

Why ui_tap_text is rated High

This tool triggers a UI interaction (tap/click) on a desktop element identified by text using the Accessibility API. It executes an action on the device/simulator, and the effect depends entirely on what element is tapped — ranging from benign navigation to triggering destructive or financial operations within apps.

From the tool's definition Tap element by text via Accessibility API (Desktop/macOS only)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ui_tap_text safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_tap_text, this is the rule to start with:

ui_tap_text Rate-limited

ui_tap_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": {
    "ui_tap_text": {
      "limits": [
        {
          "counter": "ui_tap_text_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every ui_tap_text call is checked against it from then on.

FAQ

Questions about ui_tap_text

What does the ui_tap_text tool do? +

Tap element by text via Accessibility API (Desktop/macOS only). It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ui_tap_text? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for ui_tap_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 Claude Mobile. Nothing to install.

What risk level is ui_tap_text? +

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

Can I rate-limit ui_tap_text? +

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

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

ui_tap_text is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →