tmux_split_pane
AI agents invoke tmux_split_pane 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.
Splitting a tmux pane creates a new shell/pane within a terminal session, which is an external operation that modifies the terminal environment. Given the server's purpose of controlling tmux sessions and the sibling tools (create_session, create_window, kill_pane), this tool almost certainly creates a new pane split in a tmux session. This falls under Execute as it triggers external terminal operations.
From the tool's definition Tool name 'tmux_split_pane' on a server that 'Enables Claude to control tmux sessions, manage windows and panes'; description is empty.
Attacks that exploit this kind of access
tmux_split_pane. 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 tmux_split_pane: 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.
tmux_split_pane 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_split_pane 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_split_pane. 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_split_pane 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 →