Create a new listener (HTTP, HTTPS, DNS, SMB, etc.)
AI agents invoke create_listener to trigger actions in Cobalt Strike MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating a listener in Cobalt Strike sets up an active network service that accepts incoming beacon connections from compromised hosts. This triggers an external operation with real infrastructure impact — it opens network ports and establishes command-and-control channels. It is not a simple data write; it executes operational infrastructure that enables further compromise of target systems.
From the tool's definition 'Create a new listener (HTTP, HTTPS, DNS, SMB, etc.)' on a Cobalt Strike red team operations server
Attacks that exploit this kind of access
Create a new listener (HTTP, HTTPS, DNS, SMB, etc.). It is categorised as a Execute tool in the Cobalt Strike MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_listener is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
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 →