delete_listener_dns

Delete a DNS listener

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/delete-listener-dns.md

WHAT IT DOES

What delete_listener_dns does on Cobalt Strike MCP Server

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.

RISK

Why delete_listener_dns is rated Critical

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

RECOMMENDED RULE

The rule that runs delete_listener_dns 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_dns, this is the rule to start with:

delete_listener_dns Hidden

delete_listener_dns is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_listener_dns"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every delete_listener_dns call is checked against it from then on.

FAQ

Questions about delete_listener_dns

What does the delete_listener_dns tool do? +

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.

How do I enforce a policy on delete_listener_dns? +

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.

What risk level is delete_listener_dns? +

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.

Can I rate-limit delete_listener_dns? +

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.

How do I block delete_listener_dns completely? +

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.

What MCP server provides delete_listener_dns? +

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.

KEEP EXPLORING

More on Cobalt Strike MCP Server, and thousands of servers like it.

This server

All 220 Cobalt Strike MCP Server tools → Critical-risk tools on this server →

Across the catalogue

delete_dns_record on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →