list_non_priv_users_with_admin_and_sessions
How to control list_non_priv_users_with_admin_and_sessions ↓
AI agents call list_non_priv_users_with_admin_and_sessions 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 and queries Active Directory data to identify non-privileged users who have been granted admin privileges and have active sessions. It performs reconnaissance but does not modify, delete, or execute actions on the target environment.
From the tool's definition Tool name 'list_non_priv_users_with_admin_and_sessions' indicates a query/list operation that retrieves information about users matching specific criteria (non-privileged users with admin rights and active sessions).
Documented attack patterns abuse exactly the kind of access list_non_priv_users_with_admin_and_sessions 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_non_priv_users_with_admin_and_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_non_priv_users_with_admin_and_sessions": {}
}
}list_non_priv_users_with_admin_and_sessions 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_non_priv_users_with_admin_and_sessions. 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_non_priv_users_with_admin_and_sessions: 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_non_priv_users_with_admin_and_sessions 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_non_priv_users_with_admin_and_sessions 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_non_priv_users_with_admin_and_sessions. 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_non_priv_users_with_admin_and_sessions 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.