Get log information for a specific task
AI agents call get_task_log 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.
The tool itself performs a read operation (retrieval of logs). However, the context is critical: Cobalt Strike is an adversarial tool used for unauthorized red team operations, post-exploitation, and command & control. Accessing task logs in this context could reveal sensitive operational details, exfiltrated data, or attack execution timelines.
From the tool's definition Tool name 'get_task_log' and description 'Get log information for a specific task' indicate retrieval of log data without modification. However, this is part of Cobalt Strike MCP Server which enables red team operations and beacon control—a threat actor tool.
Attacks that exploit this kind of access
Get log information for a specific task. 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_task_log: 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_task_log 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_task_log 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_task_log. 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_task_log 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_task_log 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 →