get_beacon_tokenStore

What get_beacon_tokenStore does on Cobalt Strike MCP Server

AI agents call get_beacon_tokenStore 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_tokenStore is rated Low

This is a Read operation as it retrieves beacon token store state. However, severity is elevated to 'high' rather than 'low' because: (1) Cobalt Strike is explicitly a red team/attack framework; (2) token stores contain sensitive authentication credentials that could be chained into further compromise; (3) the context of 200+ beacon control tools indicates this accesses post-exploitation data on compromised systems.

From the tool's definition Tool name 'get_beacon_tokenStore' and description 'Get token store state for beacon' indicates retrieval of credential/token data from a compromised endpoint without modification.

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

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

Questions about get_beacon_tokenStore