# kali_password_hydra_brute

Fast network login brute-forcer supporting many protocols. Hydra is a parallelized login cracker which supports numerous protocols. Supported Services: - SSH, FTP, HTTP(S), MySQL, SMB, RDP, Telnet, and more WARNING: Only use on systems you have authorization to test. Example: - SSH: target=

Agent View of the PolicyLayer registry record for `kali_password_hydra_brute`. HTML page: https://policylayer.com/tools/azza39925-kali-mcp-server/kali-password-hydra-brute

## Facts

- Tool: `kali_password_hydra_brute`
- Server: Kali MCP Server (`azza39925/kali-mcp-server`) — https://policylayer.com/tools/azza39925-kali-mcp-server.md
- Homepage: https://github.com/azza39925/kali-mcp-server
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "kali_password_hydra_brute",
    "arguments": {}
  }
}
```

## Why kali_password_hydra_brute is rated High

Hydra actively executes brute-force authentication attacks against remote systems across numerous protocols. Misuse by an AI agent could result in unauthorized access to production systems, account lockouts, legal liability, and compromise of critical infrastructure. Even with authorization controls, the blast radius of misdirected brute-force attacks is critical.

From the tool's own definition: "Fast network login brute-forcer supporting many protocols... parallelized login cracker which supports numerous protocols... SSH, FTP, HTTP(S), MySQL, SMB, RDP, Telnet"

## Use case

AI agents invoke kali_password_hydra_brute to trigger actions in Kali 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kali MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "kali_password_hydra_brute": {
      "limits": [
        {
          "counter": "kali_password_hydra_brute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Kali MCP Server (18)

- `kali_exploit_msfvenom_generate` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-exploit-msfvenom-generate.md
- `kali_network_masscan_scan` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-network-masscan-scan.md
- `kali_network_netdiscover_scan` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-network-netdiscover-scan.md
- `kali_network_nmap_discover` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-network-nmap-discover.md
- `kali_network_nmap_scan` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-network-nmap-scan.md
- `kali_network_tcpdump_capture` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-network-tcpdump-capture.md
- `kali_network_tshark_capture` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-network-tshark-capture.md
- `kali_password_hashcat_crack` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-password-hashcat-crack.md
- `kali_password_john_crack` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-password-john-crack.md
- `kali_web_ffuf_fuzz` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-web-ffuf-fuzz.md
- `kali_web_gobuster_dir` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-web-gobuster-dir.md
- `kali_web_gobuster_dns` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-web-gobuster-dns.md
- `kali_web_nikto_scan` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-web-nikto-scan.md
- `kali_web_nuclei_scan` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-web-nuclei-scan.md
- `kali_web_sqlmap_test` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-web-sqlmap-test.md
- `kali_web_wpscan_scan` — Execute — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-web-wpscan-scan.md
- `kali_exploit_searchsploit_examine` — Read — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-exploit-searchsploit-examine.md
- `kali_exploit_searchsploit_search` — Read — https://policylayer.com/tools/azza39925-kali-mcp-server/kali-exploit-searchsploit-search.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=azza39925-kali-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/azza39925-kali-mcp-server