create_listener_foreignHttp
Create a Foreign HTTP listener
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/create-listener-foreignhttp.md
What create_listener_foreignHttp does on Cobalt Strike MCP Server
AI agents invoke create_listener_foreignHttp 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_foreignHttp is rated High
Creating a Foreign HTTP listener in Cobalt Strike sets up a command-and-control (C2) channel that enables remote beacons to communicate with external infrastructure. This is an active network operation that triggers external connectivity and red team C2 operations. It is not merely writing data but executing the creation of a live network service with operational implications.
From the tool's definition 'Create a Foreign HTTP listener' — establishes a network listener for receiving beacon callbacks in a Cobalt Strike C2 infrastructure
Attacks that exploit this kind of access
The rule that runs create_listener_foreignHttp 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_foreignHttp, this is the rule to start with:
create_listener_foreignHttp 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_foreignHttp call is checked against it from then on.
Questions about create_listener_foreignHttp
Create a Foreign HTTP 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_foreignHttp: 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_foreignHttp 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_foreignHttp 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_foreignHttp. 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_foreignHttp 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