Kill (close) a window.
AI agents call kill_window to permanently remove resources in TmuxControlLib MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Killing a window in tmux terminates the window and all panes within it, closing any running processes. This action is irreversible — the window, its panes, and any unsaved terminal state are permanently destroyed. This maps clearly to the Destructive category with high severity since an AI agent could inadvertently destroy active work sessions.
From the tool's definition Kill (close) a window
Attacks that exploit this kind of access
Kill (close) a window. It is categorised as a Destructive tool in the TmuxControlLib MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TmuxControlLib MCP Server MCP server in PolicyLayer and add a rule for kill_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.
kill_window 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 kill_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 kill_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.
kill_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 →