get_beacon_tasks_detail
Get detailed task information for a specific beacon
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/get-beacon-tasks-detail.md
What get_beacon_tasks_detail does on Cobalt Strike MCP Server
AI agents call get_beacon_tasks_detail to retrieve information from Cobalt Strike MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_beacon_tasks_detail is rated Low
This tool retrieves task information about an active beacon in a Cobalt Strike operation. While it is purely a read operation (no side effects), the severity is high because the detailed task data could reveal sensitive red team operational plans, beacon status, and attack progress if exposed to an AI agent without proper controls.
From the tool's definition Tool name 'get_beacon_tasks_detail' and description 'Get detailed task information for a specific beacon' indicate data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs get_beacon_tasks_detail 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 get_beacon_tasks_detail, this is the rule to start with:
get_beacon_tasks_detail is read-only, so it stays allowed. 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 get_beacon_tasks_detail call is checked against it from then on.
Questions about get_beacon_tasks_detail
Get detailed task information for a specific beacon. 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_tasks_detail: 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_tasks_detail 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_tasks_detail 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_tasks_detail. 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_tasks_detail 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.
More on Cobalt Strike MCP Server, and thousands of servers like it.
This server
Across the catalogue