AI agents call ad_user_enum 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.
Enumeration of domain users retrieves information about user accounts in Active Directory without creating, modifying, deleting, or executing code. However, severity is medium because enumeration provides reconnaissance data that can facilitate subsequent attacks (e.g., targeting specific users for credential attacks or social engineering), making it a useful stepping stone for adversaries despite being…
From the tool's definition Tool description states "Enumerate domain users using NetExec" - enumeration is a read-only reconnaissance operation that queries domain information without modifying or executing actions with side effects.
Documented attack patterns abuse exactly the kind of access ad_user_enum gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ad_user_enum:
{
"version": "1",
"default": "deny",
"tools": {
"ad_user_enum": {}
}
}ad_user_enum 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.
Enumerate domain users using NetExec. 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 ad_user_enum: 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.
ad_user_enum 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 ad_user_enum 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 ad_user_enum. 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.
ad_user_enum is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.