New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_listener_https

Update an HTTPS listener

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about update_listener_https

What does the update_listener_https tool do? +

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.

How do I enforce a policy on update_listener_https? +

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.

What risk level is update_listener_https? +

update_listener_https is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_listener_https? +

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.

How do I block update_listener_https completely? +

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.

What MCP server provides update_listener_https? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cobalt Strike MCP Server's. Pull the full record:

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.