ldapdomaindump MCP Server

ldapdomaindump_policies

Retrieve domain password policies and fine-grained password policies (PSOs) including lockout thresholds and password length requirements from Active Directory.

Instructions

Get domain password policies and fine-grained password policies (PSOs). Returns lockout thresholds, password length requirements, etc.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hostname": "<hostname>",
      "username": "<username>",
      "password": "<password>"
    },
    "name": "ldapdomaindump_policies"
  }
}

Input Schema

Name	Required	Description
`hostname`	Yes	Domain controller hostname or IP
`username`	Yes	Username in DOMAIN\username format
`password`	Yes	Password or NTLM hash
`authType`	No	Authentication type
`useSsl`	No	Use LDAPS connection
`outputDir`	No	Output directory

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It indicates a non-destructive read operation and returns specific policy details. However, it lacks disclosure of authentication behavior, error conditions, or potential side effects (e.g., network requirements). The description is minimal but adequate.

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

Conciseness5/5

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

The description is two sentences long, efficiently stating the purpose and return value. It is front-loaded with the main action and immediately useful information. No wasted words.

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

Completeness3/5

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

Given the tool's complexity (6 parameters, 3 required, no output schema, no annotations), the description provides the essential purpose and return value but lacks context on how to use the parameters, connection behavior, and error handling. It is adequate for a simple tool but could be more complete for an LDAP interaction tool.

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

Parameters3/5

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

Input schema has 100% coverage with descriptions for all 6 parameters. The tool description does not add extra meaning beyond the schema, nor does it need to because the schema is sufficient. Baseline score of 3 applies.

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

Purpose5/5

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

Description clearly states the tool's purpose: 'Get domain password policies and fine-grained password policies (PSOs)'. The verb 'Get' and specific resources (password policies, PSOs) distinguish it from sibling tools that focus on other aspects like computers, groups, or users.

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, context of use, or when not to use it. For an LDAP tool, usage instructions (e.g., when to use with other ldapdomaindump tools) would be helpful.

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

Deploy Server