New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_listener_https

Delete an HTTPS 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-https.md

What delete_listener_https does on Cobalt Strike MCP Server

AI agents call delete_listener_https 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_https is rated Critical

This tool performs an irreversible deletion operation on active infrastructure. Even though it is a management operation within a red team tool, the deletion of a listener is a destructive action that removes operational capability and cannot be undone programmatically.

From the tool's definition Tool name 'delete_listener_https' combined with description 'Delete an HTTPS listener' indicates irreversible deletion of a listener configuration.

Questions about delete_listener_https

What does the delete_listener_https tool do? +

Delete an HTTPS 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_https? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for delete_listener_https: 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_https? +

delete_listener_https 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_https? +

Yes. Add a rate_limit block to the delete_listener_https 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_https completely? +

Set action: deny in the PolicyLayer policy for delete_listener_https. 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_https? +

delete_listener_https 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cobalt Strike MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.