[WIP] Route all user principal(s) that have control permissions to Azure Service Principals (AzSP), and route from AzSP to principal(s) (Required: azurehound)
How to control route_user_principals_to_azure_service_principals ↓
AI agents call route_user_principals_to_azure_service_principals 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 is fundamentally a query and path-finding tool that maps privilege escalation chains in Active Directory/Azure environments. While the information it reveals (control paths to Azure Service Principals) could be valuable for attackers, the tool itself only reads and analyzes existing directory data—it does not create, modify, delete, or execute actions.
From the tool's definition Tool name and description indicate it 'route[s]' and 'find[s]' principals with permissions to Azure Service Principals—a querying/tracing operation over Active Directory and Azure relationships.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access route_user_principals_to_azure_service_principals 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_user_principals_to_azure_service_principals:
{
"version": "1",
"default": "deny",
"tools": {
"route_user_principals_to_azure_service_principals": {}
}
}route_user_principals_to_azure_service_principals 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 all user principal(s) that have control permissions to Azure Service Principals (AzSP), and route from AzSP to 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_user_principals_to_azure_service_principals: 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_user_principals_to_azure_service_principals 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_user_principals_to_azure_service_principals 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_user_principals_to_azure_service_principals. 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_user_principals_to_azure_service_principals 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.