find_paths_to_azure_subscriptions
AI agents call find_paths_to_azure_subscriptions 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 information about attack paths in an Active Directory/Azure environment without modifying data. While the discovery of privilege escalation paths to Azure subscriptions is security-sensitive (justifying 'high' severity for potential misuse in reconnaissance), the tool itself performs only read operations against the BloodHound graph database.
From the tool's definition Tool name 'find_paths_to_azure_subscriptions' indicates querying/discovering attack paths to Azure resources. Sibling tools all use 'find_*' pattern which are read-only discovery operations (find_all_domain_admins, find_asreproast_users, etc.).
Documented attack patterns abuse exactly the kind of access find_paths_to_azure_subscriptions 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 find_paths_to_azure_subscriptions:
{
"version": "1",
"default": "deny",
"tools": {
"find_paths_to_azure_subscriptions": {}
}
}find_paths_to_azure_subscriptions 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.
find_paths_to_azure_subscriptions. 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 find_paths_to_azure_subscriptions: 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.
find_paths_to_azure_subscriptions 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 find_paths_to_azure_subscriptions 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 find_paths_to_azure_subscriptions. 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.
find_paths_to_azure_subscriptions is provided by the BloodHound MCP server (mordavid/bloodhound-mcp-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BloodHound MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
75 BloodHound MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.