Oops! Copilot deployed to prod. Be careful with your extensions and MCP servers

[utterances-bot]

Oops! Copilot deployed to prod. Be careful with your extensions and MCP servers | Chad’s Blog

Came across an interesting issue recently where I asked Copilot to change my MSSQL extension connection to a different database then asked it to run some queries only realize they ran against the wrong database.

https://chadbaldwin.net/2025/07/22/oops-copilot-deployed-to-prod.html

[dr00b]

Loved this, thank you.

It's a tough one because you don't want secrets in the context. But how would it know which is which otherwise? Thanks for sharing.

[chadbaldwin]

@dr00b Yup! It's a very annoying situation. Ideally, the solution would be to make it so that the MCP server could access your registered servers list or the connections list in the VS Code MSSQL extension and then have some way to stay in sync.

This issue only occurs because the MCP server has its connections hardcoded in the configuration, whereas the extension allows you to configure it within the UI. And there's nothing ensuring that the two are using the same connection.

To be honest, I bet there is a way to program the MCP server (since it runs locally) to somehow access the connections configured in the VS Code MSSQL extension and use its connection context.