key_press · Mcp Remotetouch MCP: Risk & Policy

WHAT IT DOES

What key_press does on Mcp Remotetouch

AI agents invoke key_press 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 key_press needs a policy

This tool executes remote keyboard input on another machine, which can trigger arbitrary actions depending on the key pressed (e.g., keyboard shortcuts, terminal commands, UI interactions). Since it operates remotely and can simulate any keypress with modifiers, misuse could lead to significant unintended effects on the target system.

From the tool's definition 'Press a key with optional modifier keys on the remote device' — triggers keyboard input actions on a remote Linux device over SSH

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

key_press Rate-limited

key_press 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": {
    "key_press": {
      "limits": [
        {
          "counter": "key_press_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 key_press

What does the key_press tool do? +

Press a key with optional modifier keys on the remote device. Requires /dev/uinput access. 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 key_press? +

Register the Mcp Remotetouch MCP server in PolicyLayer and add a rule for key_press: 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 key_press? +

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

Can I rate-limit key_press? +

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

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

key_press 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.