input_tap

Tap by coordinates, text, resourceId, label, or element index.\n\n

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/input-tap.md

WHAT IT DOES

What input_tap does on Claude Mobile

AI agents invoke input_tap 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 input_tap is rated High

This tool executes a tap action on a mobile device UI element, which is an external operation (simulated or real user input). It can trigger arbitrary application behaviors depending on what is tapped, such as submitting forms, navigating screens, or confirming actions. This falls under Execute as it performs device-level UI interactions with effects that depend on arguments.

From the tool's definition 'Tap by coordinates, text, resourceId, label, or element index' — triggers UI interaction on a physical/virtual device

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs input_tap 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 input_tap, this is the rule to start with:

input_tap Rate-limited

input_tap 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": {
    "input_tap": {
      "limits": [
        {
          "counter": "input_tap_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 input_tap call is checked against it from then on.

FAQ

Questions about input_tap

What does the input_tap tool do? +

Tap by coordinates, text, resourceId, label, or element index.\n\n. 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 input_tap? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for input_tap: 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 input_tap? +

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

Can I rate-limit input_tap? +

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

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

input_tap 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 →