Get User-Defined C2 listener details
AI agents call get_listener_userDefinedC2 to retrieve information from Cobalt Strike MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that retrieves listener details from a Cobalt Strike command & control infrastructure. While it performs no destructive or write operations, the severity is elevated from 'low' to 'high' because: (1) the retrieved information could expose sensitive C2 configuration, operational infrastructure, and authentication details; (2) an AI agent querying listener details could map the red team's…
From the tool's definition Tool name 'get_listener_userDefinedC2' and description 'Get User-Defined C2 listener details' indicate querying/retrieving listener configuration data without modification.
Attacks that exploit this kind of access
Get User-Defined C2 listener details. It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for get_listener_userDefinedC2: 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.
get_listener_userDefinedC2 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_listener_userDefinedC2 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 get_listener_userDefinedC2. 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.
get_listener_userDefinedC2 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 →