spawn_net_computers
Enumerate computers (spawn mode)
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/spawn-net-computers.md
What spawn_net_computers does on Cobalt Strike MCP Server
AI agents invoke spawn_net_computers 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 spawn_net_computers is rated High
In Cobalt Strike context, 'spawn mode' means the tool spawns a new process or sacrificial process to execute the enumeration, making this an Execute-category action. It is not a passive read; it actively launches a process on a compromised host to enumerate network computers.
From the tool's definition 'spawn mode' and 'Enumerate computers' — spawning a new process/beacon to perform network enumeration is an active execution operation on a Cobalt Strike red team platform
Attacks that exploit this kind of access
The rule that runs spawn_net_computers 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 spawn_net_computers, this is the rule to start with:
spawn_net_computers 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 spawn_net_computers call is checked against it from then on.
Questions about spawn_net_computers
Enumerate computers (spawn mode). 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 spawn_net_computers: 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.
spawn_net_computers 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 spawn_net_computers 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 spawn_net_computers. 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.
spawn_net_computers 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