Separate MCP SQL tool to read and write for added protection
Currently, the
run_sql can execute read and write operations. Concerned about the affect that AI queries can have on our production database, even when reviewing tool calls, it would be great to have the run_sql tool separated into run_sql_write and run_sql_read or something similar. This would allow our team to confidently run queries without concern about changing data.
