send_ctrl_c · Tmux MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_ctrl_c does on Tmux MCP Server

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

Ctrl+C sends an interrupt signal (SIGINT) to the foreground process in a tmux session. This is an external operation that can terminate running processes, stop scripts, interrupt long-running jobs, or cancel operations mid-execution.

From the tool's definition Send Ctrl+C to a tmux session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_ctrl_c Rate-limited

send_ctrl_c 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": {
    "send_ctrl_c": {
      "limits": [
        {
          "counter": "send_ctrl_c_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about send_ctrl_c

What does the send_ctrl_c tool do? +

Send Ctrl+C to a tmux session. It is categorised as a Execute tool in the Tmux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_ctrl_c? +

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

What risk level is send_ctrl_c? +

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

Can I rate-limit send_ctrl_c? +

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

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

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