AI agents call tmux_list_sessions to retrieve information from Tmux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and enumerates existing tmux session information. It has no side effects, does not execute commands, does not modify state, and does not delete data. The blast radius of misuse is minimal—an agent could discover what sessions exist, but cannot interact with their contents or cause damage through this tool alone.
From the tool's definition Tool name 'tmux_list_sessions' and description 'List all tmux sessions' indicates a query operation that retrieves session metadata (names, IDs, window count, status) without modifying or executing anything.
Attacks that exploit this kind of access
List all tmux sessions with their names, IDs, window count, and status. It is categorised as a Read tool in the Tmux MCP Server, which means it retrieves data without modifying state.
Register the Tmux MCP server in PolicyLayer and add a rule for tmux_list_sessions: 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. Nothing to install.
tmux_list_sessions 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_sessions 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_sessions. 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_sessions is provided by the Tmux MCP server (wenlixiao-cs/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 →