New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

execute_socks_stop_all

Stop all SOCKS proxies

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/execute-socks-stop-all.md

What execute_socks_stop_all does on Cobalt Strike MCP Server

AI agents call execute_socks_stop_all to permanently remove resources in Cobalt Strike MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why execute_socks_stop_all is rated Critical

Stopping all SOCKS proxies is an irreversible action that immediately terminates all active proxy connections and tunnels in a Cobalt Strike operation. This cannot be undone without reconfiguring and restarting each proxy individually.

From the tool's definition 'Stop all SOCKS proxies' - terminates all active SOCKS proxy tunnels irreversibly, disrupting active connections and tunnels

Risk signalsBulk/mass operation — affects multiple targets

Questions about execute_socks_stop_all

What does the execute_socks_stop_all tool do? +

Stop all SOCKS proxies. It is categorised as a Destructive tool in the Cobalt Strike MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on execute_socks_stop_all? +

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

execute_socks_stop_all is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit execute_socks_stop_all? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cobalt Strike MCP Server's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.