Low Risk

route_non_priv_usrs_dang_rts_grps

Route non-privileged user(s) with dangerous rights to group(s) [HIGH RAM]

How to control route_non_priv_usrs_dang_rts_grps ↓

AI agents call route_non_priv_usrs_dang_rts_grps 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

This tool queries and analyzes Active Directory to identify security relationships and privilege escalation paths. It retrieves information about non-privileged users who possess dangerous permissions to groups. Like all sibling tools on this server (find_all_*, find_owned_*, etc.), this is a Read operation that performs complex graph analysis without modifying or deleting any Active Directory objects.

From the tool's definition Tool name 'route_non_priv_usrs_dang_rts_grps' and description 'Route non-privileged user(s) with dangerous rights to group(s)' indicate data querying/analysis.

Risk signalsAdmin/system-level operation

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

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 route_non_priv_usrs_dang_rts_grps:

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

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

Go deeper

What does the route_non_priv_usrs_dang_rts_grps tool do? +

Route non-privileged user(s) with dangerous rights to group(s) [HIGH RAM]. 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 route_non_priv_usrs_dang_rts_grps? +

Register the BloodHound MCP server in PolicyLayer and add a rule for route_non_priv_usrs_dang_rts_grps: 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 route_non_priv_usrs_dang_rts_grps? +

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

Can I rate-limit route_non_priv_usrs_dang_rts_grps? +

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

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

route_non_priv_usrs_dang_rts_grps is provided by the BloodHound MCP server (stevenyu113228/bloodhound-mcp). 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.

Deterministic rules across all 106 BloodHound MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

106 BloodHound MCP tools catalogued and risk-classified — across an index of 42,500+ 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.