executeBeaconConsoleAndWait

Execute a beacon console command and wait for streamed console output.

SERVERCobalt Strike MCP Server SOURCEcobalt-strike/cobaltstrike-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cobalt-strike-cobaltstrike-mcp-server/executebeaconconsoleandwait.md

WHAT IT DOES

What executeBeaconConsoleAndWait does on Cobalt Strike MCP Server

AI agents invoke executeBeaconConsoleAndWait 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.

RISK

Why executeBeaconConsoleAndWait is rated High

This tool executes arbitrary commands on beacons (compromised hosts) controlled by Cobalt Strike. While the tool itself doesn't delete data irreversibly, it enables full remote code execution capability - an attacker could use natural language to execute any beacon command, including system commands, lateral movement, data exfiltration, or destruction.

From the tool's definition Tool executes commands through 'beacon console' - a command interface for the Cobalt Strike C2 framework. The description states it will 'Execute a beacon console command', which triggers remote code execution on compromised targets.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs executeBeaconConsoleAndWait 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 executeBeaconConsoleAndWait, this is the rule to start with:

executeBeaconConsoleAndWait Rate-limited

executeBeaconConsoleAndWait 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": {
    "executeBeaconConsoleAndWait": {
      "limits": [
        {
          "counter": "executebeaconconsoleandwait_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every executeBeaconConsoleAndWait call is checked against it from then on.

FAQ

Questions about executeBeaconConsoleAndWait

What does the executeBeaconConsoleAndWait tool do? +

Execute a beacon console command and wait for streamed console 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 executeBeaconConsoleAndWait? +

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

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

Can I rate-limit executeBeaconConsoleAndWait? +

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

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

executeBeaconConsoleAndWait is provided by the Cobalt Strike MCP Server MCP server (cobalt-strike/cobaltstrike-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cobalt Strike MCP Server, and thousands of servers like it.

This server

All 9 Cobalt Strike MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →