Pass-the-hash attack
AI agents invoke inject_pth to trigger actions in Cobalt Strike MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Pass-the-hash is an active attack technique that executes code/authentication using compromised credentials to gain unauthorized access to systems. It is part of a Cobalt Strike red team framework with 200+ offensive tools. The blast radius is critical: successful PTH injection allows privilege escalation and lateral movement across an entire domain/network without knowing plaintext passwords.
From the tool's definition Tool name 'inject_pth' and description 'Pass-the-hash attack' — this is a credential-based lateral movement technique that injects stolen NTLM hashes to authenticate as another user and execute operations in their security context.
Attacks that exploit this kind of access
Pass-the-hash attack. It is categorised as a Execute tool in the Cobalt Strike MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for inject_pth: 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_pth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the inject_pth 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_pth. 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_pth 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 →