[WIP] Users with Most Sessions [Required: sessions]
AI agents call users_with_most_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 is a Read operation: it queries and retrieves session information about users in Active Directory without modifying or deleting anything. However, severity is high because the BloodHound context suggests this tool enables reconnaissance of Active Directory for attack planning—specifically identifying high-value targets (users with many sessions), which is a critical first step in privilege escalation and…
From the tool's definition Tool name 'users_with_most_sessions' queries Active Directory to retrieve user session data. Description indicates it retrieves/lists users ranked by session count.
Documented attack patterns abuse exactly the kind of access users_with_most_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 users_with_most_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"users_with_most_sessions": {}
}
}users_with_most_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.
[WIP] Users with Most Sessions [Required: 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 users_with_most_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.
users_with_most_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 users_with_most_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 users_with_most_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.
users_with_most_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.