# getRecentEventLogTail

Get recent streamed Cobalt Strike event log output.

Agent View of the PolicyLayer registry record for `getRecentEventLogTail`. HTML page: https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/getrecenteventlogtail

## Facts

- Tool: `getRecentEventLogTail`
- Server: Cobalt Strike MCP Server (`cobalt-strike/cobaltstrike-mcp-server`) — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server.md
- Homepage: https://github.com/Cobalt-Strike/cobaltstrike-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "getRecentEventLogTail",
    "arguments": {}
  }
}
```

## Why getRecentEventLogTail is rated Low

This tool retrieves event log data from Cobalt Strike without altering or executing any operations. While the severity is high due to the sensitive nature of Cobalt Strike adversary simulation logs (which could reveal active campaign details, compromised systems, or operational security gaps), the action itself is read-only retrieval with no side effects.

From the tool's own definition: "Tool name 'getRecentEventLogTail' and description 'Get recent streamed Cobalt Strike event log output' indicate retrieval of log data without modification. The verb 'get' and action 'retrieve output' confirm read-only access."

## Use case

AI agents call getRecentEventLogTail 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Cobalt Strike MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getRecentEventLogTail": {}
  }
}
```

## Other tools on Cobalt Strike MCP Server (8)

- `executeBeaconConsoleAndWait` — Execute — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/executebeaconconsoleandwait.md
- `lintBeaconInterpreterC` — Execute — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/lintbeaconinterpreterc.md
- `runBeaconInterpreterC` — Execute — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/runbeaconinterpreterc.md
- `startCobaltStrikeWebsocketStreams` — Execute — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/startcobaltstrikewebsocketstreams.md
- `getBeaconConsoleTail` — Read — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/getbeaconconsoletail.md
- `getCobaltStrikeWebsocketStatus` — Read — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/getcobaltstrikewebsocketstatus.md
- `getDownloadedFileText` — Read — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/getdownloadedfiletext.md
- `getLiveBeaconSnapshot` — Read — https://policylayer.com/tools/cobalt-strike-cobaltstrike-mcp-server/getlivebeaconsnapshot.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=cobalt-strike-cobaltstrike-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/cobalt-strike-cobaltstrike-mcp-server