Owned: [WIP] Find all owned user with privileged access to Azure Tenancy (Required: azurehound)
AI agents call find_owned_users_with_azure_tenancy_access 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 reconnaissance by querying Active Directory and Azure metadata to identify owned users with sensitive Azure access. While it is fundamentally a Read operation (retrieves/queries data with no side effects), the severity is high because the information disclosed (privileged Azure access paths, ownership relationships, and tenancy access) could directly enable lateral movement, privilege escalation,…
From the tool's definition Tool name includes 'find' and description indicates it 'Find[s] all owned user with privileged access to Azure Tenancy' — a query operation that retrieves information about user permissions and Azure access patterns without modifying data.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access find_owned_users_with_azure_tenancy_access 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_owned_users_with_azure_tenancy_access:
{
"version": "1",
"default": "deny",
"tools": {
"find_owned_users_with_azure_tenancy_access": {}
}
}find_owned_users_with_azure_tenancy_access 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.
Owned: [WIP] Find all owned user with privileged access 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 find_owned_users_with_azure_tenancy_access: 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_owned_users_with_azure_tenancy_access 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_owned_users_with_azure_tenancy_access 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_owned_users_with_azure_tenancy_access. 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_owned_users_with_azure_tenancy_access 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.