Get a pane by index.
AI agents call get_pane 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.
This is a retrieval operation that queries the state of a tmux pane by its index. It returns information about an existing pane without side effects, making it a Read category tool. The severity is low because reading pane metadata poses minimal risk—the blast radius of misuse is limited to information disclosure of terminal session structure.
From the tool's definition Tool description states 'Get a pane by index' which retrieves pane information without modifying state. The sibling tools include 'capture_history', 'capture_pane', 'find_text', and 'extract_table' which are all read-only; destructive operations are separated…
Attacks that exploit this kind of access
Get a pane by index. 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 get_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 TmuxControlLib MCP Server. Nothing to install.
get_pane 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 get_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 get_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.
get_pane 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 →