spawn_net_user_detail · Cobalt Strike MCP Server MCP

WHAT IT DOES

What spawn_net_user_detail does on Cobalt Strike MCP Server

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

In Cobalt Strike context, 'spawn mode' means the tool forks a new process (spawns) on the target beacon to run a command — in this case 'net user detail'. This is an Execute-category action because it runs a command/process on a remote system. While retrieving user details sounds like Read, the spawn mechanism means code execution is occurring on a compromised host, elevating risk.

From the tool's definition 'spawn mode' indicates this tool spawns a new process to execute the net user detail command on a remote beacon, triggering external operations on a compromised host

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spawn_net_user_detail Rate-limited

spawn_net_user_detail 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": {
    "spawn_net_user_detail": {
      "limits": [
        {
          "counter": "spawn_net_user_detail_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 spawn_net_user_detail

What does the spawn_net_user_detail tool do? +

Get user details (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.

How do I enforce a policy on spawn_net_user_detail? +

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

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

Can I rate-limit spawn_net_user_detail? +

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

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

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