Route all owned & enabled user(s) with Dangerous Rights to group(s)
How to control route_owned_users_dangerous_rights_to_groups ↓
AI agents call route_owned_users_dangerous_rights_to_groups 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.
This tool queries Active Directory to identify and trace relationships between owned users with dangerous rights and groups. It retrieves and analyzes existing data to find security paths, which is characteristic of Read operations. While the security implications are high (identifying privilege escalation paths), the tool itself performs no side effects, modifications, or executions.
From the tool's definition Tool description states 'Route all owned & enabled user(s) with Dangerous Rights to group(s)' - the verb 'route' combined with the query nature and sibling tools (find_*) indicates this performs a read/query operation that traces relationships in Active…
Documented attack patterns abuse exactly the kind of access route_owned_users_dangerous_rights_to_groups 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_owned_users_dangerous_rights_to_groups:
{
"version": "1",
"default": "deny",
"tools": {
"route_owned_users_dangerous_rights_to_groups": {}
}
}route_owned_users_dangerous_rights_to_groups is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Route all owned & enabled user(s) with Dangerous Rights to group(s). It is categorised as a Read tool in the BloodHound MCP MCP Server, which means it retrieves data without modifying state.
Register the BloodHound MCP server in PolicyLayer and add a rule for route_owned_users_dangerous_rights_to_groups: 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.
route_owned_users_dangerous_rights_to_groups is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the route_owned_users_dangerous_rights_to_groups 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.
Set action: deny in the PolicyLayer policy for route_owned_users_dangerous_rights_to_groups. 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.
route_owned_users_dangerous_rights_to_groups 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.
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.