Delete a DNS listener
AI agents call delete_listener_dns 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.
This tool irreversibly removes a DNS listener, which cannot be undone without manual reconfiguration. While not directly moving money or executing arbitrary code, deletion of listener infrastructure is a destructive action with operational impact. The Cobalt Strike context indicates this manages active command-and-control infrastructure, making unintended deletion a high-severity risk.
From the tool's definition Tool name 'delete_listener_dns' with description 'Delete a DNS listener' indicates irreversible deletion of a listener resource.
Attacks that exploit this kind of access
Delete a DNS 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_dns: 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_dns 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_dns 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_dns. 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_dns 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 →