// SCAN REPORT

tmux-claude MCP Server

26 tools. 16 can modify or destroy data without limits.

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

Last updated: 11 Jun 2026

16 can modify or destroy data

10 read-only

26 tools total

Community server · catalogue entry verified 11/06/2026

How to control tmux-claude MCP Server ↓

TOOL MAP

What tmux-claude MCP Server exposes to your agents

Read (10) Write / Execute (14) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous tmux-claude MCP Server tools

Destructive · High terminate This tool irreversibly terminates running Claude instances and potentially cascades to child instances. Destructive · Critical vm_terminate The tool explicitly states 'permanent destruction' of a VM instance. Execute · High executeParallel This tool triggers execution of arbitrary tasks across multiple Specialist instances. Execute · High restart Restarting instances is an Execute category action because it runs/triggers an external operation (tmux instance restart) rather than merely reading or writing data.

16 of tmux-claude MCP Server's 26 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-claude MCP Server

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

Deny destructive operations

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

{
  "commit_manager_work": {
    "limits": [
      {
        "counter": "commit_manager_work_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_workspace_conflicts": {
    "limits": [
      {
        "counter": "check_workspace_conflicts_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-claude 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-CLAUDE →

Free to start. No card required.

FULL CATALOGUE

All 26 tmux-claude MCP Server tools

DESTRUCTIVE 2 tools

Destructive terminate Terminate a Claude instance and optionally its children Destructive vm_terminate Terminate a VM instance (permanent destruction)

EXECUTE 12 tools

Execute executeParallel Execute multiple tasks in parallel using Specialist instances (Manager only) Execute restart Restart a dead instance using --continue flag Execute vm_start Start a stopped VM instance Execute vm_stop Stop a running VM instance Execute distributeWork Distribute tasks across multiple Managers (Executive only) Execute enhancedSend Send a message with queuing and guaranteed delivery Execute merge_manager_work Coordinate merge of manager work back to main branch (Executive only) Execute send Send text/prompt to a Claude instance Execute spawn Spawn a new Claude instance with role and context Execute vm_bulk_create Create multiple VM instances for parallel development Execute vm_create Create a new VM instance for Claude development Execute vm_create_image Create an AMI from a VM instance

WRITE 2 tools

Write commit_manager_work Commit current work with proper git practices (Manager only) Write sync_manager_branch Sync manager branch with latest main branch changes (Manager only)

READ 10 tools

Read check_workspace_conflicts Analyze potential conflicts in shared workspace Read enhancedRead Read messages from queue without losing them Read get_workspace_status Get comprehensive status of shared workspace Read getParallelStatus Get parallel execution status for a Manager Read list List all active Claude instances Read read Read output from a Claude instance Read vm_list List all VM instances Read vm_ssh Get SSH connection information for a VM Read vm_status Get detailed status of a VM instance

EXPLORE

Related servers

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

FAQ

Questions about tmux-claude MCP Server

Can an AI agent delete data through the tmux-claude MCP Server MCP server? +

Yes. The tmux-claude MCP Server server exposes 2 destructive tools including terminate, vm_terminate. 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-claude MCP Server? +

The tmux-claude MCP Server server has 2 write tools including commit_manager_work, sync_manager_branch. 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-claude MCP Server.

How many tools does the tmux-claude MCP Server MCP server expose? +

26 tools across 3 categories: Execute, Read, Write. 10 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on tmux-claude MCP Server? +

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

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

ENFORCE POLICY ON TMUX-CLAUDE →

Free to start. No card required.

26 tmux-claude MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.