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

get_listener_tcp

Get TCP listener details

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

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/get-listener-tcp.md

What get_listener_tcp does on Cobalt Strike MCP Server

AI agents call get_listener_tcp to retrieve information from Cobalt Strike MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_listener_tcp is rated Low

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.

Questions about get_listener_tcp

What does the get_listener_tcp tool do? +

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.

How do I enforce a policy on get_listener_tcp? +

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.

What risk level is get_listener_tcp? +

get_listener_tcp is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_listener_tcp? +

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.

How do I block get_listener_tcp completely? +

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.

What MCP server provides get_listener_tcp? +

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.

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.