MCP server for dbatools — exposes SQL Server management commands as MCP tools
Three tools with complete schemas and descriptions. Tool naming follows verb_noun convention (list_, get_, invoke_). Descriptions are present and substantive (100-300 chars). Parameters are typed with constraints (enums, maxLength, min/max). However, invoke_dbatools_command lacks output schema documentation, and error handling guidance is minimal. The 'parameters' object in invoke_dbatools_command is underspecified (generic object type with no field-level schema). Safety messaging is embedded in description rather than enforced via tool annotations.
Get the full normalized help for a specific dbatools command, including parameters and examples sourced from comment-based help.
Execute a dbatools command via PowerShell and return structured JSON output. SAFETY: For any destructive or change command (Remove, Drop, Disable, Reset, etc.), always explain the consequences to the user and ask for explicit confirmation before running. Only proceed with confirm:true if the user has clearly confirmed their intent. Respect DBATOOLS_SAFE_MODE: never bypass safety checks. For any command that modifies or deletes data, double-check with the user before proceeding. Show the exact command and output for transparency. Non-readonly commands require confirm:true when safe mode is enabled.
Search and list dbatools commands. Filter by verb, noun, keyword, or risk level.
invoke_dbatools_command 'parameters' field is a generic object with no schema for nested fields. LLMs cannot infer valid parameter names or types without explicit field definitions.
No output schema documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., command name, risk level from list results).
invoke_dbatools_command safety messaging ('explain consequences, ask for confirmation') is embedded in description text rather than enforced via tool annotations (destructiveHint). LLMs may not reliably respect text-only warnings.
Error handling lacks recovery guidance. No indication of which errors are retryable, which require user input, or which are fatal. Errors from PowerShell execution are not categorized.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
SqlCredential parameter accepts username/password as plain text in JSON. While server-side, this is logged in tool call traces. Consider environment variable injection or vault-based secret management.