Remove a token from the token store
AI agents call execute_tokenStore_remove to permanently remove resources in Cobalt Strike MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes (deletes) a token from the token store in a Cobalt Strike beacon context. Removing an access token is irreversible and could eliminate captured credentials/tokens needed for lateral movement or privilege escalation. In a red team operation, tokens represent pivotal authentication artifacts, and their removal cannot be undone.
From the tool's definition 'Remove a token from the token store' - removing a token is an irreversible deletion operation
Attacks that exploit this kind of access
Remove a token from the token store. It is categorised as a Destructive tool in the Cobalt Strike MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for execute_tokenStore_remove: 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.
execute_tokenStore_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the execute_tokenStore_remove 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 execute_tokenStore_remove. 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.
execute_tokenStore_remove 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 →