tap_screen · Termux MCP Server MCP: Risk & Policy

WHAT IT DOES

What tap_screen does on Termux MCP Server

AI agents use tap_screen to create or update resources in Termux MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Termux MCP Server environment.

WHY IT NEEDS A POLICY

Why tap_screen needs a policy

An AI agent can call tap_screen faster than any human can review — one bad instruction and it creates or modifies resources in Termux MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tap_screen Rate-limited

tap_screen stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tap_screen": {
      "limits": [
        {
          "counter": "tap_screen_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Termux MCP Server, so you can run agents against it safely.

FAQ

Questions about tap_screen

What does the tap_screen tool do? +

Tap the screen at specific coordinates. It is categorised as a Write tool in the Termux MCP Server 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_screen? +

Register the Termux MCP Server MCP server in PolicyLayer and add a rule for tap_screen: 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 Termux MCP Server. Nothing to install.

What risk level is tap_screen? +

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

Can I rate-limit tap_screen? +

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

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

tap_screen is provided by the Termux MCP Server MCP server (xlisp/termux-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.