tmux_extract_table
AI agents call tmux_extract_table 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.
Despite the empty description, the tool name and context from sibling tools and the server description indicate this extracts/parses tabular data from existing terminal output. This is a read operation with no side effects. Confidence is slightly reduced due to the empty description, but the naming convention and server capabilities strongly suggest data retrieval only.
From the tool's definition Tool name is 'extract_table' and sibling tools include 'capture_history', 'capture_pane', 'find_text' — all read-only operations that retrieve terminal output without modification.
Attacks that exploit this kind of access
tmux_extract_table. 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_extract_table: 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_extract_table 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_extract_table 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_extract_table. 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_extract_table 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 →