tmux_get_window
AI agents call tmux_get_window 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.
The 'get_window' tool retrieves information about a tmux window. Despite the empty description, the semantic meaning of 'get' combined with the server's stated capability to 'search/extract text from terminal output' and the read-only nature of sibling tools strongly indicates this is a query operation with no side effects.
From the tool's definition Tool name 'get_window' indicates a retrieval operation. The sibling tools include 'capture_pane', 'capture_history', 'find_text', and 'extract_table' which are all read-only, suggesting 'get_window' follows the same pattern of querying tmux state without…
Attacks that exploit this kind of access
tmux_get_window. 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_get_window: 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_get_window 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_get_window 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_get_window. 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_get_window 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 →