Clear the command queue for a beacon
AI agents call clear_beacon_command_queue 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.
Clearing the command queue for a Cobalt Strike beacon is an irreversible operation: any pending commands staged for execution are permanently removed. This is not a simple write/update since the data (queued commands) is destroyed and cannot be recovered. In a red team operation context, losing queued commands could disrupt ongoing operations or cause loss of access.
From the tool's definition 'Clear the command queue for a beacon' — clearing a queue removes pending commands irreversibly; in a red team C2 context, queued beacon commands cannot be recovered once purged
Attacks that exploit this kind of access
Clear the command queue for a beacon. 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 clear_beacon_command_queue: 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.
clear_beacon_command_queue 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 clear_beacon_command_queue 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 clear_beacon_command_queue. 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.
clear_beacon_command_queue 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 →