delete_listener_userDefinedC2

Delete a User-Defined C2 listener

Server Cobalt Strike MCP Server mickeydb/cobalt-strike-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_listener_userDefinedC2 does on Cobalt Strike MCP Server

AI agents call delete_listener_userDefinedC2 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_userDefinedC2 needs a policy

Deleting a C2 listener is a destructive action that cannot be undone and dismantles active operational infrastructure. In the context of a Cobalt Strike server managing red team operations, this represents a critical security risk if misused by an AI agent, as it could disable or sabotage legitimate operational capabilities or be weaponized to disrupt adversary infrastructure.

From the tool's definition Tool name contains 'delete_listener' and description states 'Delete a User-Defined C2 listener' — this is an irreversible deletion operation that removes a configured command-and-control listener, a foundational component of red team infrastructure.

Questions about delete_listener_userDefinedC2

What does the delete_listener_userDefinedC2 tool do? +

Delete a User-Defined C2 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_userDefinedC2? +

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

delete_listener_userDefinedC2 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_userDefinedC2? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.