// SCAN REPORT

Tmux

19 tools. 13 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

13 can modify or destroy data

6 read-only

19 tools total

Community server · catalogue entry verified 02/07/2026

How to control Tmux ↓

TOOL MAP

What Tmux exposes to your agents

Read (6) Write / Execute (12) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Tmux tools

Destructive · High tmux_kill Killing a tmux session, window, or pane is irreversible — any running processes, unsaved state, and shell history in those panes are permanently destroyed. Execute · Critical remote_bash_execute This tool executes shell commands on remote systems via tmux, which is Execute category (runs code/commands with effects dependent on arguments). Execute · High remote_bash_connect The tool name suggests connecting to a remote bash session. Execute · High tmux_create_session Creating a tmux session spawns a new persistent shell environment.

13 of Tmux's 19 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Tmux

PolicyLayer is an MCP gateway — it sits between your AI agents and Tmux, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "tmux_kill": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "remote_bash_disconnect": {
    "limits": [
      {
        "counter": "remote_bash_disconnect_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "remote_bash_list_connections": {
    "limits": [
      {
        "counter": "remote_bash_list_connections_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Tmux — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TMUX →

Instant setup, no code required.

FULL CATALOGUE

All 19 Tmux tools

DESTRUCTIVE 1 tools

Destructive tmux_kill Kill a tmux session, window, or pane.

EXECUTE 9 tools

Execute remote_bash_connect remote_bash_connect Execute remote_bash_execute remote_bash_execute Execute tmux_create_session Create a new tmux session. Execute tmux_create_window Create a new window in an existing tmux session. Execute tmux_resize_pane tmux_resize_pane Execute tmux_select_pane Select/focus a specific tmux pane. Execute tmux_select_window Navigate/switch to a specific tmux window. Execute tmux_send_keys tmux_send_keys Execute tmux_split_window tmux_split_window

WRITE 3 tools

Write remote_bash_disconnect Disconnect an SSH connection or all connections. Write tmux_rename_session Rename a tmux session. Write tmux_rename_window Rename a tmux window.

READ 6 tools

Read remote_bash_list_connections List all active SSH connections with their status and idle time. Read tmux_list_panes List tmux panes with their IDs, dimensions, and status. Read tmux_list_sessions List all tmux sessions with their names, IDs, window count, and status. Read tmux_list_windows List all tmux windows. Optionally filter by session name or ID. Read tmux_read_cc_pane tmux_read_cc_pane Read tmux_read_pane tmux_read_pane

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Tmux

Can an AI agent delete data through the Tmux MCP server? +

Yes. The Tmux server exposes 1 destructive tools including tmux_kill. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Tmux? +

The Tmux server has 3 write tools including remote_bash_disconnect, tmux_rename_session, tmux_rename_window. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Tmux.

How many tools does the Tmux MCP server expose? +

19 tools across 3 categories: Execute, Read, Write. 6 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on Tmux? +

Register the Tmux MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Tmux tool call.

Deterministic rules across all 19 Tmux tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TMUX →

Instant setup, no code required.

19 Tmux tools catalogued and risk-classified — across an index of 43,000+ MCP servers.