// SCAN REPORT

Cmux Agent

63 tools. 42 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 12 Jun 2026

42 can modify or destroy data

21 read-only

63 tools total

Community server · catalogue entry verified 12/06/2026

How to control Cmux Agent ↓

TOOL MAP

What Cmux Agent exposes to your agents

Read (21) Write / Execute (37) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Cmux Agent tools

Destructive · Medium cmux_clear_notifications Clearing all notifications is an irreversible bulk deletion action — once notifications are cleared they cannot be recovered. Destructive · Critical cmux_close_all This tool closes all workspaces, which is an irreversible bulk destruction of session state. Destructive · High cmux_close_surface Closing a surface/tab is an irreversible action that terminates a running session or workspace. Destructive · High cmux_close_window Closing a window in a terminal multiplexer like tmux/cmux permanently destroys the window and all associated panes and running processes.

42 of Cmux Agent's 63 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Cmux Agent

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

Deny destructive operations

{
  "cmux_clear_notifications": {
    "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

{
  "cmux_new_workspace": {
    "limits": [
      {
        "counter": "cmux_new_workspace_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "cmux_browser_get": {
    "limits": [
      {
        "counter": "cmux_browser_get_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 Cmux Agent — 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 CMUX AGENT →

Free to start. No card required.

FULL CATALOGUE

All 63 Cmux Agent tools

DESTRUCTIVE 5 tools

Destructive cmux_clear_notifications Clear all notifications. Destructive cmux_close_all Close ALL workspaces (or all except specific ones). Use Destructive cmux_close_surface Close a surface (tab). Destructive cmux_close_window Close a window. Destructive cmux_close_workspace Close one or more workspaces and all their panes. Pass a single ref or an array of refs.

EXECUTE 29 tools

WRITE 8 tools

Write cmux_new_workspace Create a new workspace. Returns the workspace_ref so you can use it immediately without a follow-up list call. Write cmux_break_pane Move a pane to its own new workspace. Write cmux_move_surface Move a surface to a different pane, workspace, or window. Write cmux_move_workspace_to_window Move a workspace to a different window without closing it. Write cmux_reorder_surface Reorder a tab within its pane — change its position without closing it. Write cmux_reorder_workspace Reorder a workspace in the SIDEBAR — change its position without closing it. Write cmux_session_save Save current CMUX state (workspaces, panes, CLIs, session IDs) to a manifest for crash recovery. Call this aft Write cmux_swap_pane Swap two panes.

READ 21 tools

Read cmux_browser_get Get data from the browser page (url, title, text, html, value, attribute, element count). Read cmux_browser_screenshot Take a screenshot of the browser page. Read cmux_browser_snapshot Get a DOM accessibility snapshot of the browser page. Read cmux_current_window Get the currently focused window. Read cmux_current_workspace Get the currently active workspace. Read cmux_find Search across windows and panes by content or title. Read cmux_identify Show context info for the current CMUX session — focused window, workspace, pane, surface refs. Call this firs Read cmux_list_notifications List unread notifications. Read cmux_list_panels List all panels in a workspace. Read cmux_list_panes List all panes in a workspace. Read cmux_list_status List all sidebar status entries for a workspace. Read cmux_list_windows List all open windows. Read cmux_read_all_deep Deep read of ALL panes. For idle CLI agents, prompts them asking Read cmux_read_screen Read terminal output from a single surface. Works on all surface types. Use --scrollback to include scroll buf Read cmux_screenshot Take a screenshot of the CMUX window using macOS screencapture. Read cmux_sidebar_state Get current sidebar state (cwd, git branch, ports, status, progress, logs). Read cmux_status Check if CMUX is installed and running. Shows project config and full hierarchy. IMPORTANT: All cmux tools use Read cmux_tree Show full hierarchy tree of windows, workspaces, panes, surfaces, and panels. Read cmux_workspace_snapshot Full workspace snapshot: tree + all pane output + sidebar state. Single call for complete situational awarenes Read cmux_capture_pane Capture pane output (tmux-compatible). Works on all surface types. Read cmux_session_reconcile Compare saved session manifest against what is actually running in CMUX. Reports drift: surfaces that disappea

EXPLORE

Related servers

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

FAQ

Questions about Cmux Agent

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

Yes. The Cmux Agent server exposes 5 destructive tools including cmux_clear_notifications, cmux_close_all, cmux_close_surface. 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 Cmux Agent? +

The Cmux Agent server has 8 write tools including cmux_new_workspace, cmux_break_pane, cmux_move_surface. 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 Cmux Agent.

How many tools does the Cmux Agent MCP server expose? +

63 tools across 4 categories: Destructive, Execute, Read, Write. 21 are read-only. 42 can modify, create, or delete data.

How do I enforce a policy on Cmux Agent? +

Register the Cmux Agent 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 Cmux Agent tool call.

Deterministic rules across all 63 Cmux Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CMUX AGENT →

Free to start. No card required.

63 Cmux Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.