terminal_kill

THE RISK

Critical Risk

Why terminal_kill needs a policy

Terminating an active terminal session is a destructive action that cannot be undone without recreating the session from scratch. Any ongoing processes, unsaved work, or state within that session would be lost. Within the context of a penetration testing toolkit where sessions may be running active exploits or maintaining reverse shells, killing a session could disrupt critical operations.

From the tool's definition Tool name 'terminal_kill' combined with description 'Destroy a terminal session and free resources' indicates irreversible termination of an active session. The word 'Destroy' is explicit and unambiguous.

Documented attack patterns abuse exactly the kind of access terminal_kill gives an agent:

POLICY

How to control terminal_kill

PolicyLayer is an MCP gateway — it sits between your AI agents and Kali-Mcp-Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for terminal_kill:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "terminal_kill"
  ]
}

terminal_kill disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Kali-Mcp-Toolkit — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kali-Mcp-Toolkit tools

Execute code_execute Execute a script/program from the workspace. Execute shell_connection_exec Execute a command on a reverse-shell connection and return output. Execute shell_listener_start Start a reverse-shell listener (requires admin scope, must be enabled in config). Execute shell_listener_stop Stop a reverse-shell listener. Execute terminal_exec Execute a command in an existing terminal session. Execute exec_tool exec_tool Execute code_install_deps Install packages (requires admin scope, must be enabled in config). Execute terminal_create Create a new interactive PTY terminal session.

All 20 Kali-Mcp-Toolkit tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Kali-Mcp-Toolkit → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about terminal_kill

What does the terminal_kill tool do? +

Destroy a terminal session and free resources. It is categorised as a Destructive tool in the Kali-Mcp-Toolkit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on terminal_kill? +

Register the Kali-Mcp-Toolkit MCP server in PolicyLayer and add a rule for terminal_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 Kali-Mcp-Toolkit. Nothing to install.

What risk level is terminal_kill? +

terminal_kill is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit terminal_kill? +

Yes. Add a rate_limit block to the terminal_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.

How do I block terminal_kill completely? +

Set action: deny in the PolicyLayer policy for terminal_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.

What MCP server provides terminal_kill? +

terminal_kill is provided by the Kali-Mcp-Toolkit MCP server (trymonoly/kali-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kali-Mcp-Toolkit tool call.

Start from Kali-Mcp-Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →