List enabled user(s) with an email address
AI agents call list_enabled_users_with_email 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 Read operation that retrieves user information (enabled status, email addresses) from Active Directory. However, the severity is elevated to medium rather than low because: (1) email addresses and user lists are sensitive reconnaissance data that could enable phishing, social engineering, or targeted attacks; (2) when combined with sibling tools on this server (kerberoastable users, as-rep roastable users,…
From the tool's definition Tool name is 'list_enabled_users_with_email' and description states 'List enabled user(s) with an email address' — this retrieves/queries user data from Active Directory with no modification or execution of commands.
Documented attack patterns abuse exactly the kind of access list_enabled_users_with_email 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 list_enabled_users_with_email:
{
"version": "1",
"default": "deny",
"tools": {
"list_enabled_users_with_email": {}
}
}list_enabled_users_with_email 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.
List enabled user(s) with an email address. 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 list_enabled_users_with_email: 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.
list_enabled_users_with_email 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 list_enabled_users_with_email 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 list_enabled_users_with_email. 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.
list_enabled_users_with_email 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.