get_teamserver_ip
A read tool on the Cobalt Strike MCP server.
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/get-teamserver-ip.md
What get_teamserver_ip does on Cobalt Strike MCP Server
AI agents call get_teamserver_ip 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_teamserver_ip is rated Low
This is a Read operation—it retrieves sensitive infrastructure data (teamserver IP address) used to manage red team operations. However, severity is high rather than low because: (1) the IP address of a teamserver is critical operational security information for an attacker; (2) exposure could enable network mapping, blocking, or compromise of the C2 infrastructure; (3) in the context of a Cobalt Strike MCP server…
From the tool's definition Tool name 'get_teamserver_ip' and description 'Get teamserver IP' indicate retrieval of configuration/infrastructure information about a Cobalt Strike teamserver without modification.
Attacks that exploit this kind of access
The rule that runs get_teamserver_ip 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 get_teamserver_ip, this is the rule to start with:
get_teamserver_ip is read-only, so it stays allowed. 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 get_teamserver_ip call is checked against it from then on.
Questions about get_teamserver_ip
get_teamserver_ip is a read tool on the Cobalt Strike MCP Server MCP server. 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_teamserver_ip: 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_teamserver_ip 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_teamserver_ip 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_teamserver_ip. 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_teamserver_ip 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