run_hydra · GhostMap v2 MCP: Risk & Policy

WHAT IT DOES

What run_hydra does on GhostMap v2

AI agents invoke run_hydra to trigger actions in GhostMap v2. 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 run_hydra needs a policy

Hydra is a widely-known credential brute-force tool that executes arbitrary password attacks against target services. This is an Execute-category action (launches external tools with externally-determined parameters) with critical severity due to potential for unauthorized access to arbitrary systems. The server's stated purpose of 'attack chain synthesis' confirms offensive security operations context.

From the tool's definition Tool name 'run_hydra' refers to THC-Hydra, a password attack tool. Server context includes 'attack chain synthesis' and 'evasion capabilities'. Empty description increases uncertainty slightly but tool name is definitive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_hydra Rate-limited

run_hydra 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": {
    "run_hydra": {
      "limits": [
        {
          "counter": "run_hydra_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 GhostMap v2, so you can run agents against it safely.

FAQ

Questions about run_hydra

What does the run_hydra tool do? +

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

How do I enforce a policy on run_hydra? +

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

What risk level is run_hydra? +

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

Can I rate-limit run_hydra? +

Yes. Add a rate_limit block to the run_hydra 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 run_hydra completely? +

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

run_hydra is provided by the GhostMap v2 MCP server (samir12218415/ghostmap-v2-ai-augmented-recon-framework-with-mcp-and-cve-pipeline). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.