tmux_list_panes
AI agents call tmux_list_panes to retrieve information from TmuxControlLib MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations are Read category—they retrieve information about tmux panes without side effects. The verb 'list' and consistent naming with other Read tools on the server ('get_*', 'capture_*', 'find_text', 'extract_table') confirm this is a non-destructive query. Low severity because pane enumeration poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'tmux_list_panes' indicates listing/querying panes. Sibling tools like 'get_pane', 'get_session', 'get_window', 'capture_pane' and 'capture_history' are all Read operations.
Attacks that exploit this kind of access
tmux_list_panes. It is categorised as a Read tool in the TmuxControlLib MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TmuxControlLib MCP Server MCP server in PolicyLayer and add a rule for tmux_list_panes: 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_list_panes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tmux_list_panes 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_list_panes. 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_list_panes 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 →