Create a new tmux session. If no name is provided, tmux will generate one. Returns session name.
AI agents invoke tmux_create_session 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.
Creating a tmux session establishes a new terminal environment that can subsequently be used to execute arbitrary commands. While the creation itself is not destructive or financial, it sets up an execution context. The server description explicitly mentions 'command execution' and 'SSH access', making this an Execute-category action with medium severity since it opens a shell environment that could be misused.
From the tool's definition Create a new tmux session... Enables programmatic control over tmux terminal sessions for SSH access, command execution, and terminal automation
Attacks that exploit this kind of access
Create a new tmux session. If no name is provided, tmux will generate one. Returns session name. 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.
Register the Tmux MCP Server MCP server in PolicyLayer and add a rule for tmux_create_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 Tmux MCP Server. Nothing to install.
tmux_create_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tmux_create_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.
Set action: deny in the PolicyLayer policy for tmux_create_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.
tmux_create_session is provided by the Tmux MCP Server MCP server (mediocretriumph/tmux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →