spawn_command_runAs · Cobalt Strike MCP Server MCP

WHAT IT DOES

What spawn_command_runAs does on Cobalt Strike MCP Server

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

This tool executes arbitrary commands with user impersonation capabilities, making it Execute category. Severity is critical because: (1) it enables arbitrary code execution on target systems; (2) it can run with elevated privileges via runAs; (3) in a red team tool like Cobalt Strike, it represents a primary attack vector; (4) misuse by an AI agent could compromise any system the beacon has access to.

From the tool's definition Tool performs 'Run a command as a specific user' (direct quote), enabling execution of arbitrary commands with elevated or alternate user privileges on compromised systems. This is core Cobalt Strike beacon functionality for command execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spawn_command_runAs Rate-limited

spawn_command_runAs 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_command_runAs": {
      "limits": [
        {
          "counter": "spawn_command_runas_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_command_runAs

What does the spawn_command_runAs tool do? +

Run a command as a specific user. 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_command_runAs? +

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

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

Can I rate-limit spawn_command_runAs? +

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

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

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