Query user data from BloodHound info_type options: info - General user properties and attributes admin_rights - machine/objects this user has admin rights on constrained_delegation - services this use can delegate to via kerberos controllables - objects this use can control (WriteOwner, GenericAl...
AI agents call user_info to retrieve information from BloodHound MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries user data from BloodHound's Active Directory dataset. All listed info_type options are read-only lookups (properties, rights, memberships, etc.) with no indication of write or execute side effects.
From the tool's definition Query user data from BloodHound — info_type options include general properties, admin rights, memberships, delegation, controllables, controllers, DCOM rights, PSRemote rights, RDP rights
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access user_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BloodHound MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for user_info:
{
"version": "1",
"default": "deny",
"tools": {
"user_info": {}
}
}user_info 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.
Query user data from BloodHound info_type options: info - General user properties and attributes admin_rights - machine/objects this user has admin rights on constrained_delegation - services this use can delegate to via kerberos controllables - objects this use can control (WriteOwner, GenericAll, etc.) controllers - principals that have control over this user dcom_rights - machines this user can execute DCOM on memberships - groups this user belongs to ps_remote_rights - machines this user can PSRemote to rdp_rights - machines this user can RDP to sessions - machines this user has active sessions sql_admin_rights - SQL servers this user is admin on Args: user_id: BloodHound object ID of the user (required) info_type: what to retrieve (default: info) limit: Max Results (default 100, useful in large environments) skip: Pagination offset (default 0). It is categorised as a Read tool in the BloodHound MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BloodHound MCP Server MCP server in PolicyLayer and add a rule for user_info: 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 Server. Nothing to install.
user_info 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 user_info 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 user_info. 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.
user_info is provided by the BloodHound MCP Server MCP server (mwnickerson/bloodhound_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BloodHound MCP Server, 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.
13 BloodHound MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.