remote_bash_connect · Tmux MCP: Risk & Policy

WHAT IT DOES

What remote_bash_connect does on Tmux

AI agents invoke remote_bash_connect to trigger actions in Tmux. 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 remote_bash_connect needs a policy

The tool name suggests connecting to a remote bash session. While the description is empty (lowering confidence), the sibling tools 'remote_bash_execute' and 'remote_bash_disconnect' strongly imply this establishes a remote shell connection that can execute arbitrary commands.

From the tool's definition Tool name 'remote_bash_connect' on a server that provides 'remote_bash_execute' sibling tool; implies establishing a remote bash shell connection

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remote_bash_connect Rate-limited

remote_bash_connect 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": {
    "remote_bash_connect": {
      "limits": [
        {
          "counter": "remote_bash_connect_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 Tmux, so you can run agents against it safely.

FAQ

Questions about remote_bash_connect

What does the remote_bash_connect tool do? +

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

How do I enforce a policy on remote_bash_connect? +

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

What risk level is remote_bash_connect? +

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

Can I rate-limit remote_bash_connect? +

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

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

remote_bash_connect is provided by the Tmux MCP server (wenlixiao-cs/tmux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.