MssqlMcp: Incorrect tool tags - 'List Tables' marked as destructive, 'Create Table' marked as read-only
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start by locating the MssqlMcp tool definitions for ListTables, CreateTable, DescribeTable, InsertData, UpdateData, and DropTable. Compare each tag with the operation it performs, then review the available tools in Claude Desktop or VS Code to confirm read operations do not appear destructive and schema-changing operations are appropriately marked.
Written by the indexing model from the issue text.
Description
Problem
The MssqlMcp .NET server has incorrect tool tags that misrepresent the nature of operations:
Current (incorrect) behavior:
ListTablesis tagged as destructiveCreateTableis tagged as read-onlyDescribeTableis tagged as read-only ✓ (correct)
Expected behavior:
ListTablesshould be tagged as read-only (it only queries metadata via INFORMATION_SCHEMA or sys tables)CreateTableshould be tagged as destructive or write (it modifies database schema)- Other write operations (
InsertData,UpdateData,DropTable) should also be reviewed for correct tagging
Impact
This causes user confusion and may trigger unnecessary confirmations for safe read operations while failing to warn about actual schema modifications.
Environment
- MssqlMcp version: Built from main branch (dotnet implementation)
- .NET 8.0
- MCP SDK: Official C# SDK
Steps to Reproduce
- Configure MssqlMcp server in Claude Desktop or VS Code
- View available tools
- Observe incorrect tags on
ListTables(destructive) andCreateTable(read-only)
Additional Context
The tool tags appear to be swapped or misconfigured in the tool definitions. ListTables performs a SELECT query on database metadata and should be completely safe/read-only.
- Dominant language
- HTML
- Stars
- 331
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure-Samples/SQL-AI-samples
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure-Samples/SQL-AI-samples#79 · 6 reactions ·
-
Local db Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Azure-Samples/SQL-AI-samples
Similar issues
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
confluentinc/dbt-confluent#160 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
AstrBotDevs/AstrBot#10205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100