Update 2025-07-22-oops-copilot-deployed-to-prod.md

Author: chadbaldwin

_posts/2025-07-22-oops-copilot-deployed-to-prod.md

@@ -15,7 +15,7 @@ The short of it is...I asked Copilot to change the connection used by the MSSQL
 
 So let's set up a worst case scenario and see what happens.
 
----
+----
 
 ## Setting up the environment
 
@@ -54,6 +54,8 @@ And finally, it's time to set up the MCP server connection. In this case, I'm go
 }
 ```
 
+----
+
 ## Let's deploy to prod by accident on purpose
 
 We're finally ready to cause some problems. By this point you should have everything set up and ready to go...VS Code, Copilot, Agent Mode, two databases to play with, MSSQL Extension with a database connection configured for each database and the MSSQL MCP Server configured to point at the production connection string.
@@ -94,6 +96,8 @@ The problem is that Copilot is unaware of what happens within an MCP server, nor
 
 Unfortunately, Copilot has no idea what's going on inside of an MCP server. All it knows about is the output provided back to it and in the case of creating our table, the MCP server simply returned a success message. It had no idea the server actually connected to an entirely different database.
 
+----
+
 ## Moral of the story?
 
-Mind your P's and Q's. As long as the MCP server requires a hard-coded connection string for its connection, this problem is going to exist and it's going to pop up. I wouldn't be surprised if this hasn't already caused some problems.
+Mind your P's and Q's. As long as the MCP server requires a hard-coded connection string for its connection, this problem is going to exist and it's going to pop up. I wouldn't be surprised if this hasn't already caused some problems.