create_listener_foreignHttps
Create a Foreign HTTPS listener
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/create-listener-foreignhttps.md
What create_listener_foreignHttps does on Cobalt Strike MCP Server
AI agents invoke create_listener_foreignHttps 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.
Why create_listener_foreignHttps is rated High
Creating a Foreign HTTPS listener establishes a live external command-and-control endpoint that can receive connections from compromised beacons. This is an Execute-level action because it triggers an external network operation and activates C2 infrastructure. While it creates a persistent configuration, the primary concern is that it enables ongoing red team (or adversarial) operations.
From the tool's definition 'Create a Foreign HTTPS listener' — creates an active network listener in a Cobalt Strike C2 infrastructure, enabling inbound beacon connections over HTTPS
Attacks that exploit this kind of access
The rule that runs create_listener_foreignHttps 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 create_listener_foreignHttps, this is the rule to start with:
create_listener_foreignHttps stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every create_listener_foreignHttps call is checked against it from then on.
Questions about create_listener_foreignHttps
Create a Foreign HTTPS listener. 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_foreignHttps: 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_foreignHttps 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_foreignHttps 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_foreignHttps. 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_foreignHttps 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.
Across the catalogue