Enumerate users (spawn mode)
AI agents invoke spawn_net_user 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.
The tool spawns a process to enumerate users on a target system. 'Spawn mode' means it creates a new process/thread to run the enumeration, making it Execute rather than Read. In a Cobalt Strike context, spawning processes for reconnaissance is an active offensive operation with significant blast radius — it can trigger EDR alerts, leave forensic artifacts, and is part of post-exploitation tradecraft.
From the tool's definition 'spawn mode' indicates spawning a process to enumerate users; part of Cobalt Strike beacon operations
Attacks that exploit this kind of access
Enumerate users (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_user: 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_user 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_user 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_user. 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_user 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →