kill_beacon

Kill/remove a beacon from the teamserver

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp

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/mickeydb-cobalt-strike-mcp/kill-beacon.md

WHAT IT DOES

What kill_beacon does on Cobalt Strike MCP Server

AI agents call kill_beacon to permanently remove resources in Cobalt Strike MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why kill_beacon is rated Critical

Killing a beacon irreversibly terminates an agent session and removes it from the teamserver. While not destructive to target systems, it permanently removes an operational capability and cannot be undone without re-deploying.

From the tool's definition Tool name 'kill_beacon' and description 'Kill/remove a beacon from the teamserver' indicates irreversible termination of an active beacon agent.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs kill_beacon safely

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

kill_beacon Hidden

kill_beacon 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_beacon"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every kill_beacon call is checked against it from then on.

FAQ

Questions about kill_beacon

What does the kill_beacon tool do? +

Kill/remove a beacon from the teamserver. It is categorised as a Destructive tool in the Cobalt Strike MCP Server 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_beacon? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for kill_beacon: 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 Cobalt Strike MCP Server. Nothing to install.

What risk level is kill_beacon? +

kill_beacon 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_beacon? +

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

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

kill_beacon is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cobalt Strike MCP Server, and thousands of servers like it.

This server

All 220 Cobalt Strike MCP Server 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 →