execute_socks5_start · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_socks5_start does on Cobalt Strike MCP Server

AI agents invoke execute_socks5_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 IT NEEDS A POLICY

Why execute_socks5_start needs a policy

This tool triggers the execution of a SOCKS5 proxy service on a compromised host, which is a significant operational action with broad effects. It enables an attacker to route traffic through the compromised system to access internal network resources, pivot to other systems, and conduct further attacks.

From the tool's definition 'Start SOCKS5 proxy' - initiates a network proxy service that redirects traffic through a beacon, enabling arbitrary network operations and command execution within a compromised network.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_socks5_start Rate-limited

execute_socks5_start stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cobalt Strike MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_socks5_start

What does the execute_socks5_start tool do? +

Start SOCKS5 proxy. It is categorised as a Execute tool in the Cobalt Strike MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_socks5_start? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for execute_socks5_start: 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 execute_socks5_start? +

execute_socks5_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_socks5_start? +

Yes. Add a rate_limit block to the execute_socks5_start 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 execute_socks5_start completely? +

Set action: deny in the PolicyLayer policy for execute_socks5_start. 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 execute_socks5_start? +

execute_socks5_start 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.

// THE FULL RECORD

execute_socks5_start is one line of Cobalt Strike MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →