enumerate users on an active directory domain, you can provide username or password if you have some
AI agents call enumerate_domain_users to retrieve information from PentestMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though enumerate_domain_users only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
enumerate users on an active directory domain, you can provide username or password if you have some. It is categorised as a Read tool in the PentestMCP MCP Server, which means it retrieves data without modifying state.
Register the Pentest MCP server in PolicyLayer and add a rule for enumerate_domain_users: 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 PentestMCP. Nothing to install.
enumerate_domain_users 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 enumerate_domain_users 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 enumerate_domain_users. 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.
enumerate_domain_users is provided by the Pentest MCP server (youssefsahnoun/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.