Delete an HTTP listener
AI agents call delete_listener_http 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.
Deletion of listeners cannot be undone and removes active command-and-control infrastructure. This is a destructive operation with high blast radius in an active red team engagement. While not directly financial or affecting target systems, it irreversibly destroys operational infrastructure, placing it in the Destructive category above Execute.
From the tool's definition Tool name 'delete_listener_http' and description 'Delete an HTTP listener' indicate irreversible deletion of infrastructure configuration. The server context (Cobalt Strike red team operations) confirms this manages persistent listener infrastructure.
Attacks that exploit this kind of access
Delete an HTTP listener. 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 delete_listener_http: 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.
delete_listener_http 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 delete_listener_http 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 delete_listener_http. 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.
delete_listener_http 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 →