New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

execute_tokenStore_remove

Remove a token from the token store

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/execute-tokenstore-remove.md

What execute_tokenStore_remove does on Cobalt Strike MCP Server

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.

Why execute_tokenStore_remove is rated Critical

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

Questions about execute_tokenStore_remove

What does the execute_tokenStore_remove tool do? +

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.

How do I enforce a policy on execute_tokenStore_remove? +

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.

What risk level is execute_tokenStore_remove? +

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.

Can I rate-limit execute_tokenStore_remove? +

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.

How do I block execute_tokenStore_remove completely? +

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.

What MCP server provides execute_tokenStore_remove? +

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cobalt Strike MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.