Create a new tmux session.
AI agents invoke create_session to trigger actions in TmuxControlLib 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 triggers an external process/environment in the operating system. While it doesn't delete data or execute arbitrary code directly, it establishes a persistent terminal session that can be used to run commands, making it an Execute-category action. Severity is medium because the session itself is a container for further actions, and misuse could lead to uncontrolled terminal environments.
From the tool's definition "Create a new tmux session" — spawns a new tmux session, which is an external system-level operation
Attacks that exploit this kind of access
Create a new tmux session. It is categorised as a Execute tool in the TmuxControlLib MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TmuxControlLib MCP Server MCP server in PolicyLayer and add a rule for 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 TmuxControlLib MCP Server. Nothing to install.
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 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 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.
create_session is provided by the TmuxControlLib MCP Server MCP server (jbwinters/tmuxcontrollib). 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 →