Feature: Allow dirty reads (SQL READ_UNCOMMITTED / NOLOCK)

[BartKofoed]

Hi all,

First of all, thank you for providing this very useful tool.

I'm building an AI agent that accesses a SQL database through MCP. This database is also used by an ERP application that runs 24/7. Some of the tables are quite large, so queries issued through MCP can take a while to complete — and since they run under the default READ COMMITTED isolation level, they end up blocking other operations on the database for that duration. RCSI isn't enabled on this database, and we're reluctant to enable it, since it would change read behavior for the ERP application as well, not just for the AI agent.

The AI agent is mainly used for reporting and insights, so occasional dirty reads are an acceptable tradeoff for us. My suggestion would be to add an option for READ UNCOMMITTED / WITH (NOLOCK), so that MCP queries can explicitly opt into dirty reads and reduce their impact on the ERP system's concurrent operations.

I'd appreciate your thoughts and ideas on this.

Kind regards,
Bart