Dump Chrome passwords
AI agents call inject_chromedump 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.
While credential exfiltration is a serious attack capability, the tool itself performs a read-only operation—it retrieves existing data without creating, modifying, or destroying information. The high severity reflects the sensitive nature of the data (passwords) and the potential for credential misuse, but the category is Read because the underlying operation is data retrieval.
From the tool's definition Tool name 'inject_chromedump' and description 'Dump Chrome passwords' indicate credential extraction from the Chrome browser. The verb 'dump' in this context means to retrieve and exfiltrate stored data without modification.
Attacks that exploit this kind of access
Dump Chrome passwords. 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 inject_chromedump: 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.
inject_chromedump 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 inject_chromedump 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 inject_chromedump. 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.
inject_chromedump 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 →