kill

Kill process. Auto-selects client.

SERVERClaude C2 SOURCE0xyg3n/claude-c2

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xyg3n-claude-c2/kill.md

WHAT IT DOES

What kill does on Claude C2

AI agents call kill to permanently remove resources in Claude C2, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why kill is rated Critical

Killing a process is an irreversible action that immediately terminates execution of that process. In the context of a remote command-and-control server, this could disrupt critical system services, security tools, or user applications on remote machines. The 'auto-selects client' feature means it can act across multiple remote systems with minimal input.

From the tool's definition Tool name 'kill' with description 'Kill process. Auto-selects client.' — terminates running processes irreversibly on remote systems

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs kill safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kill, this is the rule to start with:

kill Hidden

kill is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every kill call is checked against it from then on.

FAQ

Questions about kill

What does the kill tool do? +

Kill process. Auto-selects client. It is categorised as a Destructive tool in the Claude C2 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 kill? +

Register the Claude C2 MCP server in PolicyLayer and add a rule for 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 Claude C2. Nothing to install.

What risk level is kill? +

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 kill? +

Yes. Add a rate_limit block to the 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 kill completely? +

Set action: deny in the PolicyLayer policy for 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 kill? +

kill is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude C2, and thousands of servers like it.

This server

All 94 Claude C2 tools → Critical-risk tools on this server →

Across the catalogue

kill_ftp_session on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →