Low Risk

find_paths_to_privileged_roles

find_paths_to_privileged_roles

How to control find_paths_to_privileged_roles ↓

What find_paths_to_privileged_roles does on BloodHound MCP

AI agents call find_paths_to_privileged_roles to retrieve information from BloodHound MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why find_paths_to_privileged_roles needs a policy

This tool retrieves or queries data from BloodHound—specifically, paths to privileged roles in Active Directory. It performs no modifications, deletions, or code execution.

From the tool's definition Tool name 'find_paths_to_privileged_roles' indicates querying attack paths in Active Directory; sibling tools like 'find_all_domain_admins' and 'find_asreproast_users' are clearly Read operations querying BloodHound data.

Documented attack patterns abuse exactly the kind of access find_paths_to_privileged_roles gives an agent:

How to control find_paths_to_privileged_roles

PolicyLayer is an MCP gateway — it sits between your AI agents and BloodHound MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for find_paths_to_privileged_roles:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_paths_to_privileged_roles": {}
  }
}

find_paths_to_privileged_roles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BloodHound MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about find_paths_to_privileged_roles

What does the find_paths_to_privileged_roles tool do? +

find_paths_to_privileged_roles. It is categorised as a Read tool in the BloodHound MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_paths_to_privileged_roles? +

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

What risk level is find_paths_to_privileged_roles? +

find_paths_to_privileged_roles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_paths_to_privileged_roles? +

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

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

find_paths_to_privileged_roles is provided by the BloodHound MCP server (mordavid/bloodhound-mcp-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BloodHound MCP tool call.

Start from BloodHound MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

75 BloodHound MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.