getLiveBeaconSnapshot

Get the latest streamed beacon snapshot.

SERVERCobalt Strike MCP Server SOURCEcobalt-strike/cobaltstrike-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cobalt-strike-cobaltstrike-mcp-server/getlivebeaconsnapshot.md

WHAT IT DOES

What getLiveBeaconSnapshot does on Cobalt Strike MCP Server

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

RISK

Why getLiveBeaconSnapshot is rated Low

Although this tool operates within a Cobalt Strike C2 framework context (used for adversary simulation), the tool itself performs only data retrieval—accessing status/state information about active beacons. No code execution, data modification, deletion, or financial actions occur.

From the tool's definition Tool name 'getLiveBeaconSnapshot' and description 'Get the latest streamed beacon snapshot' indicate retrieval of existing data without modification. The verb 'Get' and absence of any write/execute/delete language confirms read-only semantics.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getLiveBeaconSnapshot 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 getLiveBeaconSnapshot, this is the rule to start with:

getLiveBeaconSnapshot Allowed

getLiveBeaconSnapshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getLiveBeaconSnapshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every getLiveBeaconSnapshot call is checked against it from then on.

FAQ

Questions about getLiveBeaconSnapshot

What does the getLiveBeaconSnapshot tool do? +

Get the latest streamed beacon snapshot. It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getLiveBeaconSnapshot? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for getLiveBeaconSnapshot: 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.

What risk level is getLiveBeaconSnapshot? +

getLiveBeaconSnapshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getLiveBeaconSnapshot? +

Yes. Add a rate_limit block to the getLiveBeaconSnapshot 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.

How do I block getLiveBeaconSnapshot completely? +

Set action: deny in the PolicyLayer policy for getLiveBeaconSnapshot. 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.

What MCP server provides getLiveBeaconSnapshot? +

getLiveBeaconSnapshot is provided by the Cobalt Strike MCP Server MCP server (cobalt-strike/cobaltstrike-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cobalt Strike MCP Server, and thousands of servers like it.

This server

All 9 Cobalt Strike MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →