Get token store state for beacon
AI agents call get_beacon_tokenStore 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.
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.
Attacks that exploit this kind of access
Get token store state for 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_tokenStore: 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_tokenStore 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_tokenStore 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_tokenStore. 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_tokenStore 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →