Terminates the process and cleans up resources.
AI agents call kill_session to permanently remove resources in Interactive Terminal MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Killing a process and cleaning up its resources is an irreversible action. Any unsaved state, in-flight operations, or persistent sessions (SSH, debuggers, REPLs) will be permanently destroyed. This cannot be undone, placing it in the Destructive category. Severity is high because it can abruptly end critical sessions (e.g., active SSH connections, running scripts) with potential data loss or system disruption.
From the tool's definition 'Terminates the process and cleans up resources' — irreversible termination of a running process and cleanup of associated resources.
Documented attack patterns abuse exactly the kind of access kill_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Interactive Terminal MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for kill_session:
{
"version": "1",
"default": "deny",
"hide": [
"kill_session"
]
}kill_session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Terminates the process and cleans up resources. It is categorised as a Destructive tool in the Interactive Terminal MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Interactive Terminal 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 Interactive Terminal MCP. 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 Interactive Terminal MCP server (wangyihang/interactive-terminal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Interactive Terminal MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Interactive Terminal MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.