spawn_command_runNoOutput · Cobalt Strike MCP Server MCP

WHAT IT DOES

What spawn_command_runNoOutput does on Cobalt Strike MCP Server

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

This tool executes arbitrary commands on remote beacons without returning output, enabling attackers to run malicious payloads silently. In the context of Cobalt Strike (a commercial adversarial simulation framework), this represents remote code execution with no observability constraints.

From the tool's definition Tool name includes 'spawn_command' and description states 'Run command without output'. The Cobalt Strike MCP Server explicitly provides 'beacon control' and 'payload generation' for 'red team operations'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spawn_command_runNoOutput Rate-limited

spawn_command_runNoOutput 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_runNoOutput": {
      "limits": [
        {
          "counter": "spawn_command_runnooutput_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_runNoOutput

What does the spawn_command_runNoOutput tool do? +

Run command without output. 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_runNoOutput? +

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

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

Can I rate-limit spawn_command_runNoOutput? +

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

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

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