List all windows in a tmux session.
AI agents call list_windows to retrieve information from Post-Exploitation tmux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays information about tmux windows. It performs no write, execute, destructive, or financial operations. The action is purely informational, making it a Read category tool with low severity since listing windows poses minimal security risk even if misused by an agent.
From the tool's definition Tool name is 'list_windows' and description states 'List all windows in a tmux session' — this is a query operation that retrieves information about existing tmux windows with no modification or side effects.
Attacks that exploit this kind of access
List all windows in a tmux session. It is categorised as a Read tool in the Post-Exploitation tmux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Post-Exploitation tmux MCP Server MCP server in PolicyLayer and add a rule for list_windows: 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 Post-Exploitation tmux MCP Server. Nothing to install.
list_windows 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 list_windows 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 list_windows. 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.
list_windows is provided by the Post-Exploitation tmux MCP Server MCP server (raghavansv/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 →