Skip to main content
Glama

enumerate_domain_users

Identify users in an Active Directory domain by scanning IP addresses, optionally using credentials to discover accounts for security testing.

Instructions

enumerate users on an active directory domain, you can provide username or password if you have some

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipsYes
usernameNo
passwordNo

Implementation Reference

  • The handler function decorated with @mcp.tool for registration. Executes netexec smb --users on the provided IP addresses to enumerate domain users, optionally using provided username and password credentials.
    @mcp.tool(name="enumerate_domain_users",description="enumerate users on an active directory domain, you can provide username or password if you have some")
    def enumerate_domain_users(ips:List[str],username="",password=""):
        if len(username)>0:
            if len(password)>0:
                return run_command(["netexec","smb"]+ips+["-u",username,"-p",password,"--users"])
    
            return run_command(["netexec","smb"]+ips+["-u",username,"--users"])
        return run_command(["netexec","smb"]+ips+["--users"])
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions authentication parameters (username/password) but fails to describe critical traits such as whether this is a read-only operation, potential impacts on the domain (e.g., detection risks), rate limits, or expected output format. This leaves significant gaps for a tool that interacts with Active Directory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is somewhat front-loaded but includes unnecessary phrasing ('if you have some'). It could be more direct, e.g., 'Enumerate users on an Active Directory domain with optional authentication.' However, it avoids excessive verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of domain enumeration, no annotations, no output schema, and low schema coverage, the description is inadequate. It lacks details on behavior, output, error handling, and security implications, making it incomplete for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions 'username or password' but doesn't explain their purpose or format, and omits the 'ips' parameter entirely. This adds minimal value beyond the schema, failing to clarify semantics like what 'ips' represents (domain controllers?) or authentication requirements.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'enumerate' and the resource 'users on an active directory domain', which specifies what the tool does. It distinguishes itself from siblings like 'bruteforce_rid_users' or 'Kerberoast' by focusing on enumeration rather than attack techniques. However, it doesn't explicitly mention how it differs in scope or method from similar tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal guidance with 'you can provide username or password if you have some', implying authentication is optional but not clarifying when to use this tool versus alternatives like 'bloodhound_ingest' or 'list_saved_quereis'. No explicit when/when-not scenarios or prerequisites are stated, leaving usage context vague.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YoussefSahnoun/PentestMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server