hydra_brute · Redteam MCP: Risk & Policy

WHAT IT DOES

What hydra_brute does on Redteam

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

WHY IT NEEDS A POLICY

Why hydra_brute needs a policy

Hydra is a widely recognized credential brute-force/attack tool. Even with an empty description, the tool name 'hydra_brute' on a red team / penetration testing server strongly indicates it executes brute-force password attacks against remote services (SSH, FTP, HTTP, etc.). This is an active offensive operation that could compromise accounts and systems, warranting critical severity.

From the tool's definition Tool name 'hydra_brute' on a penetration testing server running hacking tools in Kali Linux Docker container; Hydra is a well-known password brute-forcing tool used to attack authentication services.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hydra_brute Rate-limited

hydra_brute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hydra_brute": {
      "limits": [
        {
          "counter": "hydra_brute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Redteam, so you can run agents against it safely.

FAQ

Questions about hydra_brute

What does the hydra_brute tool do? +

hydra_brute. It is categorised as a Execute tool in the Redteam MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hydra_brute? +

Register the Redteam MCP server in PolicyLayer and add a rule for hydra_brute: 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 Redteam. Nothing to install.

What risk level is hydra_brute? +

hydra_brute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hydra_brute? +

Yes. Add a rate_limit block to the hydra_brute 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.

How do I block hydra_brute completely? +

Set action: deny in the PolicyLayer policy for hydra_brute. 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.

What MCP server provides hydra_brute? +

hydra_brute is provided by the Redteam MCP server (samirjani03/redteam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.