AI agents invoke tmux_resize_pane to trigger actions in Tmux. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Resizing a tmux pane is a UI/session management action that modifies the state of a running tmux session. It fits best under Execute (triggers an external operation affecting a running process environment). The description is empty, lowering confidence. Severity is medium because misuse could disrupt running terminal sessions, but it does not directly destroy data or execute arbitrary commands.
From the tool's definition Tool name 'tmux_resize_pane' on a server that 'allows AI assistants to create, manage, and interact with tmux sessions, windows, and panes programmatically'; description is empty.
Attacks that exploit this kind of access
tmux_resize_pane. It is categorised as a Execute tool in the Tmux MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tmux MCP server in PolicyLayer and add a rule for tmux_resize_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 Tmux. Nothing to install.
tmux_resize_pane is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tmux_resize_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 tmux_resize_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.
tmux_resize_pane 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 →