[WIP] Route from Azure User principal(s) that have dangerous rights to Azure User and User principal(s) (Required: azurehound)
How to control route_azure_users_with_dangerous_rights_to_users ↓
AI agents call route_azure_users_with_dangerous_rights_to_users 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 performs read-only graph traversal and analysis of Azure AD relationships to identify risky privilege paths. While the information retrieved (dangerous rights) is sensitive and could inform an attacker, the tool itself only retrieves and queries existing data without creating, modifying, deleting, or executing actions.
From the tool's definition Tool name contains 'route' and 'find' semantic; description states it routes/queries from Azure User principals with dangerous rights. The verb 'route' in BloodHound context means path traversal analysis (querying relationships), not modifying or executing.
Documented attack patterns abuse exactly the kind of access route_azure_users_with_dangerous_rights_to_users 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_azure_users_with_dangerous_rights_to_users:
{
"version": "1",
"default": "deny",
"tools": {
"route_azure_users_with_dangerous_rights_to_users": {}
}
}route_azure_users_with_dangerous_rights_to_users 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.
[WIP] Route from Azure User principal(s) that have dangerous rights to Azure User and User principal(s) (Required: azurehound). 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_azure_users_with_dangerous_rights_to_users: 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_azure_users_with_dangerous_rights_to_users 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_azure_users_with_dangerous_rights_to_users 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_azure_users_with_dangerous_rights_to_users. 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_azure_users_with_dangerous_rights_to_users 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.