executeBeaconConsoleAndWait
Execute a beacon console command and return untrusted task-result output.
This record as markdown: /tools/cobalt-strike-cobaltstrike-mcp-server/executebeaconconsoleandwait.md
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.
Why executeBeaconConsoleAndWait is rated High
The tool runs arbitrary commands on compromised endpoints via Cobalt Strike beacons. While ostensibly for 'adversary simulation workflows,' an AI agent given control over beacon command execution can perform reconnaissance, lateral movement, data exfiltration, or malware deployment—all high-impact offensive operations whose effects cannot be predicted without inspecting the command string.
From the tool's definition Tool executes a 'beacon console command' through Cobalt Strike C2 framework (adversary simulation). This directly triggers external operations with effects dependent on the command argument.
Attacks that exploit this kind of access
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 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.
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.
Questions about executeBeaconConsoleAndWait
Execute a beacon console command and return untrusted task-result 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.
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.
executeBeaconConsoleAndWait 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 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.
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.
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.
More on Cobalt Strike MCP Server, and thousands of servers like it.
Across the catalogue