Skip to main content
Glama

nxc_smb

Execute SMB protocol commands to enumerate Windows systems, validate credentials, execute commands, and dump credentials. Supports pass-the-hash attacks.

Instructions

Execute NetExec SMB protocol commands for Windows enumeration, credential validation, command execution, and credential dumping. Supports pass-the-hash attacks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget IP, hostname, CIDR range, or file path containing targets
usernameNoUsername for authentication
passwordNoPassword for authentication
hashNoNTLM hash for pass-the-hash (format: LM:NT or :NT)
domainNoDomain name for authentication
localAuthNoUse local authentication instead of domain
actionNoAction to perform
commandNoCommand to execute (for exec-cmd or exec-ps actions)
moduleNoModule to run (e.g., lsassy, mimikatz, spider_plus)
moduleOptionsNoModule options (key=value format)
continueOnSuccessNoContinue spraying after successful auth
threadsNoNumber of concurrent threads (default: 100)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions credential dumping and pass-the-hash but does not disclose risks (e.g., account lockout, admin requirements) or non-obvious behaviors. The dangerous actions (sam, lsa, ntds) are listed without warnings.

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?

Two sentences clearly convey purpose and a key feature (pass-the-hash). No redundant information. Every word earns its place.

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?

For a complex tool with 12 parameters and no output schema, the description is too brief. It omits common usage patterns, error behavior, privilege requirements, and output expectations, leaving the agent under-informed.

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?

Schema coverage is 100%, so baseline is 3. The description adds high-level context (enumeration, validation, etc.) but does not explain when to use specific actions or parameter interactions beyond what the schema already provides.

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 it executes NetExec SMB protocol commands for enumeration, validation, execution, and dumping, and explicitly mentions pass-the-hash. This distinguishes it from sibling tools targeting other protocols (e.g., nxc_ldap, nxc_mssql).

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 tool versus alternatives, no prerequisites, and no scenarios. It only lists capabilities without contextual advice.

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