Kill a tmux session, window, or pane.
AI agents call tmux_kill to permanently remove resources in Tmux — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Killing a tmux session, window, or pane is irreversible — any running processes, unsaved state, and shell history in those panes are permanently destroyed. This is a destructive action with no undo mechanism.
From the tool's definition Kill a tmux session, window, or pane
Attacks that exploit this kind of access
Kill a tmux session, window, or pane. It is categorised as a Destructive tool in the Tmux MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tmux MCP server in PolicyLayer and add a rule for tmux_kill: 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_kill is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tmux_kill 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_kill. 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_kill 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 →