tap

// WHEN AI AGENTS USE THIS TOOL

AI agents use tap to create or modify resources in Scrcpy. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON TAP

Without a policy, an AI agent could call tap repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Scrcpy.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-juancf-scrcpy-mcp.yaml

tools:
  tap:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Scrcpy policy for all 38 tools.

// DETAILS

Tool Name tap

Category Write

MCP Server Scrcpy MCP Server

Risk Level Medium

// MORE SCRCPY TOOLS

Destructive app_uninstall Execute app_start Execute app_stop Execute screen_record_start Execute screen_record_stop Execute shell_exec Execute start_session Execute start_video_stream

View all 38 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like tap have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the tap tool do? +

Tap at the specified screen coordinates. It is categorised as a Write tool in the Scrcpy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tap? +

Add a rule in your Intercept YAML policy under the tools section for tap. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Scrcpy MCP server.

What risk level is tap? +

tap is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tap? +

Yes. Add a rate_limit block to the tap rule in your Intercept 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 tap completely? +

Set action: deny in the Intercept policy for 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 tap? +

tap is provided by the Scrcpy MCP server (scrcpy-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Scrcpy