Route non-privileged computer(s) with dangerous rights to GPO(s) [HIGH RAM]
How to control route_non_priv_comps_dangerous_rights_to_gpos ↓
AI agents call route_non_priv_comps_dangerous_rights_to_gpos 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 retrieves and analyzes Active Directory relationships (computers with dangerous rights to GPOs) through query operations. No description indicates it modifies, executes code, or deletes data.
From the tool's definition Tool name indicates 'Route...to' and 'find/query' pattern consistent with sibling tools (find_all_enabled_as_rep_roastable_users, find_allshortestpaths_with_dcsync_to_domain).
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access route_non_priv_comps_dangerous_rights_to_gpos 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_comps_dangerous_rights_to_gpos:
{
"version": "1",
"default": "deny",
"tools": {
"route_non_priv_comps_dangerous_rights_to_gpos": {}
}
}route_non_priv_comps_dangerous_rights_to_gpos 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 non-privileged computer(s) with dangerous rights to GPO(s) [HIGH RAM]. 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_non_priv_comps_dangerous_rights_to_gpos: 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_non_priv_comps_dangerous_rights_to_gpos 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_non_priv_comps_dangerous_rights_to_gpos 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_non_priv_comps_dangerous_rights_to_gpos. 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_non_priv_comps_dangerous_rights_to_gpos 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.