tmux_send_command · TmuxControlLib MCP Server MCP

WHAT IT DOES

What tmux_send_command does on TmuxControlLib MCP Server

AI agents invoke tmux_send_command to trigger actions in TmuxControlLib MCP Server. 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 tmux_send_command needs a policy

The tool name strongly implies sending commands to a tmux session/pane, which executes arbitrary shell commands in a terminal. This is one of the most dangerous capabilities possible — an AI agent could run any shell command on the host system. The description is empty, which lowers confidence slightly, but the name and server context make the Execute classification nearly certain.

From the tool's definition Tool name 'tmux_send_command' on a server designed to 'control tmux sessions' and 'manage windows and panes'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tmux_send_command Rate-limited

tmux_send_command 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": {
    "tmux_send_command": {
      "limits": [
        {
          "counter": "tmux_send_command_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 TmuxControlLib MCP Server, so you can run agents against it safely.

FAQ

Questions about tmux_send_command

What does the tmux_send_command tool do? +

tmux_send_command. It is categorised as a Execute tool in the TmuxControlLib MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tmux_send_command? +

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

What risk level is tmux_send_command? +

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

Can I rate-limit tmux_send_command? +

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

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

tmux_send_command is provided by the TmuxControlLib MCP Server MCP server (jbwinters/tmuxcontrollib). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.