execute_socks_stop_port · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_socks_stop_port does on Cobalt Strike MCP Server

AI agents invoke execute_socks_stop_port 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_socks_stop_port needs a policy

This tool executes a command to stop a SOCKS proxy service on a specified port. While not directly destructive (the proxy can be restarted), it is an Execute category action because it triggers an external operation whose effects depend on the port argument and directly impacts system services.

From the tool's definition Tool name contains 'execute' and description states 'Stop SOCKS proxy on specific port', indicating it triggers external operations that modify running services. Server context is 'Cobalt Strike red team operations' with 'beacon control' capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_socks_stop_port Rate-limited

execute_socks_stop_port 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_socks_stop_port": {
      "limits": [
        {
          "counter": "execute_socks_stop_port_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_socks_stop_port

What does the execute_socks_stop_port tool do? +

Stop SOCKS proxy on specific port. 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_socks_stop_port? +

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

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

Can I rate-limit execute_socks_stop_port? +

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

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

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