Dump logon passwords using Mimikatz
AI agents call spawn_logon_passwords 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.
Although credential dumping has severe security implications (credentials could be misused), the tool's primary function is to *retrieve* sensitive data rather than execute arbitrary code, delete data, or move money. This falls under the Read category as credential extraction is fundamentally a data retrieval operation.
From the tool's definition Tool name 'spawn_logon_passwords' and description 'Dump logon passwords using Mimikatz' - the action is credential extraction/dumping, which retrieves sensitive authentication data from memory without modification or deletion of the passwords themselves.
Attacks that exploit this kind of access
Dump logon passwords using Mimikatz. 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 spawn_logon_passwords: 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.
spawn_logon_passwords 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 spawn_logon_passwords 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 spawn_logon_passwords. 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.
spawn_logon_passwords 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 →