Network login brute-force tool. Supports SSH, FTP, HTTP, RDP, and many other protocols.
AI agents invoke hydra_bruteforce to trigger actions in MCP Kali Pentest. 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.
Hydra performs active brute-force credential attacks against live network services across multiple protocols. This executes external attack operations against target systems, making it Execute category. Severity is critical because misuse can compromise remote systems, violate unauthorized access laws, and cause account lockouts across SSH, RDP, FTP, and HTTP services at scale.
From the tool's definition 'Network login brute-force tool. Supports SSH, FTP, HTTP, RDP, and many other protocols.'
Attacks that exploit this kind of access
Network login brute-force tool. Supports SSH, FTP, HTTP, RDP, and many other protocols. It is categorised as a Execute tool in the MCP Kali Pentest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for hydra_bruteforce: 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 MCP Kali Pentest. Nothing to install.
hydra_bruteforce 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 hydra_bruteforce 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 hydra_bruteforce. 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.
hydra_bruteforce is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). 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 →