touch_connect · Mcp Remotetouch MCP: Risk & Policy

WHAT IT DOES

What touch_connect does on Mcp Remotetouch

AI agents invoke touch_connect to trigger actions in Mcp Remotetouch. 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.

WHY IT NEEDS A POLICY

Why touch_connect needs a policy

This tool establishes an SSH connection to a remote device and starts a daemon process. It initiates external operations (SSH session, daemon execution) on a remote machine. This is an Execute-category action because it triggers external operations; the blast radius is high since it grants persistent remote control capability over another device's touchscreen input system.

From the tool's definition Connect to a remote Linux device via SSH and start the touch daemon

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

touch_connect Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about touch_connect

What does the touch_connect tool do? +

Connect to a remote Linux device via SSH and start the touch daemon. Returns a session ID for subsequent touch commands. It is categorised as a Execute tool in the Mcp Remotetouch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on touch_connect? +

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

What risk level is touch_connect? +

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

Can I rate-limit touch_connect? +

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

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

touch_connect is provided by the Mcp Remotetouch MCP server (signal-slot/mcp-remotetouch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.