execute_socks4_start

What execute_socks4_start does on Cobalt Strike MCP Server

AI agents invoke execute_socks4_start 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_socks4_start is rated High

This tool triggers execution of a network service (SOCKS4 proxy) whose side effects (traffic routing, potential data interception, access to internal networks) are external and difficult to predict or undo. While not destructive or financial, the blast radius is critical in an adversarial AI context: an agent could pivot attacks, tunnel malicious traffic, or expose internal services.

From the tool's definition Tool named 'execute_socks4_start' described as 'Start SOCKS4 proxy' on a Cobalt Strike red team operations server. The verb 'execute' and 'start' indicate triggering an external operation (proxy startup).

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

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

Questions about execute_socks4_start