delete_listener
Delete/remove a listener from the teamserver
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/delete-listener.md
What delete_listener does on Cobalt Strike MCP Server
AI agents call delete_listener 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.
Why delete_listener is rated Critical
Deleting a listener from a Cobalt Strike teamserver is an irreversible operation that destroys a configured network component. This cannot be undone without manual reconfiguration. In the context of red team operations, a listener is a critical infrastructure component for command and control. Destruction of listeners is irreversible and represents loss of operational capability.
From the tool's definition Tool name is 'delete_listener' and description states 'Delete/remove a listener from the teamserver'. The use of 'Delete' and 'remove' indicates irreversible removal of a configured listener resource.
Attacks that exploit this kind of access
The rule that runs delete_listener 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 delete_listener, this is the rule to start with:
delete_listener is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every delete_listener call is checked against it from then on.
Questions about delete_listener
Delete/remove a listener 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 delete_listener: 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 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 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. 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 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.
More on Cobalt Strike MCP Server, and thousands of servers like it.
Across the catalogue