create_tmux_session · Hacker MCP: Risk & Policy

WHAT IT DOES

What create_tmux_session does on HackerMCP

AI agents invoke create_tmux_session 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 create_tmux_session needs a policy

Creating a tmux session establishes a persistent shell environment that can be used to run arbitrary commands, including penetration testing tools. In the context of this server (HackerMCP, with sibling tools like run_in_tmux, start_msfconsole, nmapscan), this is an Execute-category action that sets up an execution context.

From the tool's definition 'Create a new tmux session' in the context of a server described as enabling access to penetration testing tools like Nmap and Metasploit

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_tmux_session Rate-limited

create_tmux_session 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": {
    "create_tmux_session": {
      "limits": [
        {
          "counter": "create_tmux_session_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 create_tmux_session

What does the create_tmux_session tool do? +

Create a new 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 create_tmux_session? +

Register the Hacker MCP server in PolicyLayer and add a rule for create_tmux_session: 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 create_tmux_session? +

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

Can I rate-limit create_tmux_session? +

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

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

create_tmux_session 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.