run_blooodhound_query · Pentest MCP: Risk & Policy

WHAT IT DOES

What run_blooodhound_query does on PentestMCP

AI agents invoke run_blooodhound_query to trigger actions in PentestMCP. 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_blooodhound_query needs a policy

run_blooodhound_query triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_blooodhound_query Rate-limited

run_blooodhound_query 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_blooodhound_query": {
      "limits": [
        {
          "counter": "run_blooodhound_query_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 PentestMCP, so you can run agents against it safely.

FAQ

Questions about run_blooodhound_query

What does the run_blooodhound_query tool do? +

Run a bloodhound cypher query of your choice (use this to collect information about the network and potentially identify attack vectors). It is categorised as a Execute tool in the PentestMCP 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_blooodhound_query? +

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

What risk level is run_blooodhound_query? +

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

Can I rate-limit run_blooodhound_query? +

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

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

run_blooodhound_query is provided by the Pentest MCP server (youssefsahnoun/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.