Kill (destroy) a tmux session and all its windows/panes.
AI agents call kill_session to permanently remove resources in Post-Exploitation tmux MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Killing a tmux session destroys the session object and terminates all associated windows and panes. This is an irreversible operation that cannot be undone and results in loss of session state. While the server claims guardrails prevent 'destructive system operations,' the tool itself performs a destructive action on tmux infrastructure.
From the tool's definition Tool name explicitly uses 'kill' and description states it will 'destroy' a tmux session and 'all its windows/panes' — irreversible termination of session state and any running processes within.
Attacks that exploit this kind of access
Kill (destroy) a tmux session and all its windows/panes. It is categorised as a Destructive tool in the Post-Exploitation tmux MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Post-Exploitation tmux MCP Server MCP server in PolicyLayer and add a rule for kill_session: 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 Post-Exploitation tmux MCP Server. Nothing to install.
kill_session 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_session 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_session. 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_session is provided by the Post-Exploitation tmux MCP Server MCP server (raghavansv/tmux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
kill_session is one line of Post-Exploitation tmux MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →