Skip to main content
Glama

nxc_ldap

Enumerate Active Directory users, groups, and computers; perform Kerberoasting, ASREP roasting, and BloodHound collection over LDAP.

Instructions

Execute NetExec LDAP protocol commands for Active Directory enumeration, including users, groups, Kerberoasting, and BloodHound collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget domain controller IP or hostname
usernameNoUsername for authentication
passwordNoPassword for authentication
hashNoNTLM hash for pass-the-hash
domainNoDomain name
actionNoAction to perform
bloodhoundCollectionNoBloodHound collection method (All, DCOnly, etc.)
moduleNoModule to run (e.g., adcs, daclread, maq)
outputFileNoOutput file path for results
threadsNoNumber of concurrent threads
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only vs. destructive actions, authentication requirements, rate limits, or side effects. The description simply states 'execute commands' without clarifying impact.

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 a single, concise sentence that front-loads the main purpose. No extraneous information is present.

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?

With 10 parameters, a rich enum, and no output schema, the description is too brief to be fully informative. It fails to explain how actions work, output format, or error handling, making it incomplete for a complex 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?

The input schema has 100% description coverage for all 10 parameters. The description adds examples of actions (users, groups, etc.) but does not significantly enhance meaning beyond the schema's own descriptions. With full schema coverage, the description's incremental value is limited.

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?

The description clearly states the tool executes NetExec LDAP protocol commands for Active Directory enumeration, listing specific actions like users, groups, Kerberoasting, and BloodHound collection. This distinguishes it from sibling tools that target other protocols (e.g., SMB, RDP).

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 no guidance on when to use this LDAP tool versus alternatives like nxc_smb or nxc_ldap is implied, but no explicit conditions, prerequisites, or exclusions are mentioned.

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/schwarztim/sec-netexec-mcp'

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