Get TCP listener details
AI agents call get_listener_tcp 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 tool retrieves listener details (a read operation) with no side effects. However, severity is elevated to 'high' due to the context of a Cobalt Strike red team operation server where listener details—such as ports, callback addresses, encryption keys, or authentication tokens—represent sensitive reconnaissance data that could enable or escalate attacks if disclosed to an unauthorized AI agent.
From the tool's definition Tool name 'get_listener_tcp' with description 'Get TCP listener details' indicates a read-only query operation that retrieves configuration or status information about TCP listeners without modifying or executing anything.
Attacks that exploit this kind of access
Get TCP 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_tcp: 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_tcp 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_tcp 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_tcp. 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_tcp 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 →