update_listener_https
Update an HTTPS listener
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/update-listener-https.md
What update_listener_https does on Cobalt Strike MCP Server
AI agents use update_listener_https to create or update resources in Cobalt Strike MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cobalt Strike MCP Server environment.
Why update_listener_https is rated Medium
This tool updates/modifies an existing HTTPS listener in a Cobalt Strike red team environment. It's a Write operation (modifying existing configuration), but carries high severity because listener configurations in C2 frameworks directly affect beacon communications, attacker infrastructure, and potentially active red team operations. Misuse could disrupt or redirect C2 traffic.
From the tool's definition 'Update an HTTPS listener' — modifies an existing listener configuration reversibly
Attacks that exploit this kind of access
The rule that runs update_listener_https 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 update_listener_https, this is the rule to start with:
update_listener_https stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 update_listener_https call is checked against it from then on.
Questions about update_listener_https
Update an HTTPS listener. It is categorised as a Write tool in the Cobalt Strike MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for update_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.
update_listener_https is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_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.
This server
Across the catalogue