Select a specific pane in a tmux session to make it active for commands.
AI agents invoke tmux_select_pane 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.
This tool changes the active pane in a tmux session, which directs where subsequent commands will be sent. While the action itself is a UI/state change, it is part of a terminal automation workflow and directly influences command execution targeting.
From the tool's definition Select a specific pane in a tmux session to make it active for commands
Attacks that exploit this kind of access
Select a specific pane in a tmux session to make it active for commands. 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_select_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 Tmux MCP Server. Nothing to install.
tmux_select_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_select_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_select_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_select_pane 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 →