batch_send_keys · Ai Mcp Terminal MCP: Risk & Policy

WHAT IT DOES

What batch_send_keys does on Ai Mcp Terminal

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

Given the server context (multi-threaded terminal management enabling async command execution) and the tool name 'batch_send_keys', this tool almost certainly sends keyboard input to one or more terminal sessions in batch. Sending keystrokes to terminals can execute arbitrary commands, making this an Execute-category tool with high severity. Confidence is reduced due to the empty description.

From the tool's definition Tool exists on a terminal management MCP server with sibling tools like execute_command, broadcast_command, execute_batch — all execution-oriented. The name 'batch_send_keys' implies sending keystrokes to multiple terminals in batch.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_send_keys Rate-limited

batch_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": {
    "batch_send_keys": {
      "limits": [
        {
          "counter": "batch_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 batch_send_keys

What does the batch_send_keys tool do? +

batch_send_keys. 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 batch_send_keys? +

Register the Ai Mcp Terminal MCP server in PolicyLayer and add a rule for batch_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 batch_send_keys? +

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

Can I rate-limit batch_send_keys? +

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

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

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