Get the output from a beacon (console output)
AI agents call get_beacon_output to retrieve information from Cobalt Strike MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While the operation itself is read-only (retrieves data without side effects), the severity is elevated to 'high' rather than 'low' because: (1) the server context is Cobalt Strike, a tool designed for offensive operations against systems; (2) beacon output typically contains results from reconnaissance, credential theft, or system enumeration; (3) an AI agent with this capability could extract sensitive data from…
From the tool's definition The tool retrieves console output from a beacon without modifying or destroying data. The description states it 'Get[s] the output from a beacon (console output)' - a read operation.
Attacks that exploit this kind of access
Get the output from a beacon (console output). It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for get_beacon_output: 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.
get_beacon_output is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_beacon_output 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 get_beacon_output. 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.
get_beacon_output 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →