send_keys · Ai Mcp Terminal MCP: Risk & Policy

WHAT IT DOES

What send_keys does on Ai Mcp Terminal

AI agents invoke send_keys to trigger actions in Ai Mcp Terminal. 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 send_keys needs a policy

This tool sends keystrokes and text directly to a terminal session, enabling arbitrary command execution and control of interactive programs. Since it can inject any input into a live terminal (including executing commands, editing files, or controlling shell sessions), it falls under Execute.

From the tool's definition Send any key or text to terminal... Interactive command input, command line editing, vim/nano operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_keys Rate-limited

send_keys 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": {
    "send_keys": {
      "limits": [
        {
          "counter": "send_keys_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 Ai Mcp Terminal, so you can run agents against it safely.

FAQ

Questions about send_keys

What does the send_keys tool do? +

v1.0.2: Send any key or text to terminal. Supports all keyboard keys: letters, numbers, symbols, function keys (F1-F12), control keys (Ctrl+X), arrow keys, etc. Can send single key or full string. Use cases: Interactive command input, command line editing, vim/nano operations, etc. It is categorised as a Execute tool in the Ai Mcp Terminal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_keys? +

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

What risk level is send_keys? +

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

Can I rate-limit send_keys? +

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

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

send_keys is provided by the Ai Mcp Terminal MCP server (kanniganfan/ai-mcp-terminal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.