run_in_tmux · Hacker MCP: Risk & Policy

WHAT IT DOES

What run_in_tmux does on HackerMCP

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

This tool directly executes arbitrary commands whose effects depend entirely on user/agent input. In a penetration testing MCP context, it provides unrestricted code execution capability. Blast radius is critical: an AI agent given this tool could launch attacks, exfiltrate data, or compromise systems.

From the tool's definition Tool runs arbitrary commands in tmux sessions. Combined with server context (Nmap, Metasploit penetration testing tools) and sibling tools like start_msfconsole, this enables execution of any shell command, including network attacks, exploit delivery, and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_in_tmux Rate-limited

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

FAQ

Questions about run_in_tmux

What does the run_in_tmux tool do? +

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

How do I enforce a policy on run_in_tmux? +

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

What risk level is run_in_tmux? +

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

Can I rate-limit run_in_tmux? +

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

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

run_in_tmux is provided by the Hacker MCP server (r3versein/hackermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.