[WIP] Route all principal(s) that have control permissions to Azure Application(s) running as Azure Service Principals (AzSP), and route from privileged ASP to Azure Tenancy (Required: azurehound)
AI agents call route_principals_to_azure_apps_and_sps 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 a reconnaissance/query tool that identifies security principals and their control relationships across Azure infrastructure. While the output reveals sensitive privilege escalation paths that could enable attacks, the tool itself performs only read operations against existing Azure AD/Azure objects. It does not execute actions, modify permissions, delete data, or commit financial obligations.
From the tool's definition Tool description indicates it 'routes' and identifies principals with 'control permissions to Azure Application(s)' and traces paths 'from privileged ASP to Azure Tenancy.' The verb 'route' combined with the analysis scope suggests querying/traversing…
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access route_principals_to_azure_apps_and_sps 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_principals_to_azure_apps_and_sps:
{
"version": "1",
"default": "deny",
"tools": {
"route_principals_to_azure_apps_and_sps": {}
}
}route_principals_to_azure_apps_and_sps 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 principal(s) that have control permissions to Azure Application(s) running as Azure Service Principals (AzSP), and route from privileged ASP to Azure Tenancy (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_principals_to_azure_apps_and_sps: 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_principals_to_azure_apps_and_sps 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_principals_to_azure_apps_and_sps 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_principals_to_azure_apps_and_sps. 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_principals_to_azure_apps_and_sps 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.