execute_socks5_start
Start SOCKS5 proxy
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/execute-socks5-start.md
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 execute_socks5_start is rated High
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
The rule that runs execute_socks5_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_socks5_start, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every execute_socks5_start call is checked against it from then on.
Questions about execute_socks5_start
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.
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.
execute_socks5_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Cobalt Strike MCP Server, and thousands of servers like it.
Across the catalogue