execute_net_domain

What execute_net_domain does on Cobalt Strike MCP Server

AI agents invoke execute_net_domain to trigger actions in Cobalt Strike MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why execute_net_domain is rated High

Despite the description sounding like a read operation, this tool is part of a Cobalt Strike beacon control suite and the 'execute_net_' naming convention indicates it executes a 'net domain' command remotely on a compromised host. In the context of Cobalt Strike operations, this constitutes remote code/command execution on a target system, not a simple local query.

From the tool's definition Tool name 'execute_net_domain' on a Cobalt Strike MCP server; description says 'Get domain information' but the 'execute_net_' prefix indicates it runs a net command on a beacon (remote execution of OS-level commands in a red team context).

The rule that runs execute_net_domain 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 execute_net_domain, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_net_domain": {
      "limits": [
        {
          "counter": "execute_net_domain_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about execute_net_domain