Kill/remove a beacon from the teamserver
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.
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
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.
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.
kill_beacon 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_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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →