// SCAN REPORT

Tmux MCP Server

8 tools. 7 can modify or destroy data without limits.

7 write tools that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

7 can modify or destroy data

1 read-only

8 tools total

Community server · catalogue entry verified 29/06/2026

How to control Tmux MCP Server ↓

TOOL MAP

What Tmux MCP Server exposes to your agents

Read (1) Write / Execute (7) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Tmux MCP Server tools

Execute · High launch_agent Despite empty description, the tool name 'launch_agent' in a tmux automation context indicates spawning or executing an external agent/process. Execute · High start_auto_cycle This tool triggers automated execution of tmux workflows (exit/continue cycles) whose effects depend on the tmux session state and configured automation rules. Execute · High start_message_timer This tool executes automated, repeated commands to a tmux session based on configurable parameters (message content, timing, target session). Execute · High stop_auto_cycle This tool triggers termination of an automated process running in a tmux session.

7 of Tmux MCP Server's 8 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 MCP Server

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

Cap read operations

{
  "list_tmux_sessions": {
    "limits": [
      {
        "counter": "list_tmux_sessions_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 MCP Server — 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 8 Tmux MCP Server tools

EXECUTE 7 tools

Execute launch_agent launch_agent Execute send_ctrl_c Send Ctrl+C to a tmux session Execute send_message_to_session Send a message to a specific tmux session Execute start_auto_cycle start_auto_cycle Execute start_message_timer Start a timer to repeatedly send a message to a tmux session Execute stop_auto_cycle Stop an active auto-cycle for a tmux session Execute stop_message_timer Stop an active message timer for a tmux session

READ 1 tools

Read list_tmux_sessions List all active tmux sessions

EXPLORE

Related servers

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

FAQ

Questions about Tmux MCP Server

Is the Tmux MCP Server MCP server safe to use without restrictions? +

The Tmux MCP Server server is primarily read-only with 1 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Tmux MCP Server MCP server expose? +

8 tools across 3 categories: Execute, Read, Write. 1 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Tmux MCP Server? +

Register the Tmux MCP Server 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 MCP Server tool call.

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

ENFORCE POLICY ON TMUX →

Instant setup, no code required.

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