bloodhound_ingest · MCP Kali Pentest MCP: Risk & Policy

WHAT IT DOES

What bloodhound_ingest does on MCP Kali Pentest

AI agents invoke bloodhound_ingest 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.

WHY IT NEEDS A POLICY

Why bloodhound_ingest needs a policy

BloodHound ingestion involves actively collecting data from Active Directory environments (via SharpHound or similar collectors), which executes network operations against domain controllers and AD infrastructure. It identifies privilege escalation paths, making it a critical offensive security tool. In a pentest framework context, misuse could expose full domain attack paths enabling complete network compromise.

From the tool's definition 'Active Directory attack path analysis. Identifies privilege escalation paths.' — actively queries and analyzes AD environments to find exploitation routes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bloodhound_ingest Rate-limited

bloodhound_ingest 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": {
    "bloodhound_ingest": {
      "limits": [
        {
          "counter": "bloodhound_ingest_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 MCP Kali Pentest, so you can run agents against it safely.

FAQ

Questions about bloodhound_ingest

What does the bloodhound_ingest tool do? +

Active Directory attack path analysis. Identifies privilege escalation paths. 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.

How do I enforce a policy on bloodhound_ingest? +

Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for bloodhound_ingest: 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.

What risk level is bloodhound_ingest? +

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

Can I rate-limit bloodhound_ingest? +

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

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

bloodhound_ingest 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.