Get help for a specific beacon command
AI agents call get_beacon_command_help 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.
This tool queries help documentation for beacon commands rather than executing, creating, modifying, or deleting data. It is informational in nature. However, the medium severity reflects the context that this MCP server manages Cobalt Strike (an adversarial red team framework), so even read access to command help could facilitate malicious operations if an AI agent is compromised or misaligned.
From the tool's definition Tool name is 'get_beacon_command_help' and description states it 'Get help for a specific beacon command' — this retrieves documentation or help text without executing commands or modifying state.
Attacks that exploit this kind of access
Get help for a specific beacon command. 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_command_help: 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_command_help 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_command_help 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_command_help. 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_command_help 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.
get_beacon_command_help is one line of Cobalt Strike MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →