---
title: "Comment by Ahmet Özel on \"Why we stopped letting AI agents connect directly to the database\" | Hashnode"
description: "Replay also needs a consistency boundary across the agreed tables. An open-orders contract and a stock-balance contract can each return valid read-only results"
url: "https://hashnode.com/posts/why-we-stopped-letting-ai-agents-connect-directly-to-the-database/6aed07a2ff2dd3fb23aa5b7d/comment/6af15786bf36fdf837b4885b"
---

[Discussion](https://hashnode.com/posts/why-we-stopped-letting-ai-agents-connect-directly-to-the-database/6aed07a2ff2dd3fb23aa5b7d)

Comment [Why we stopped letting AI agents connect directly to the database](https://hashnode.com/posts/why-we-stopped-letting-ai-agents-connect-directly-to-the-database/6aed07a2ff2dd3fb23aa5b7d)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[4d ago](https://hashnode.com/posts/why-we-stopped-letting-ai-agents-connect-directly-to-the-database/6aed07a2ff2dd3fb23aa5b7d/comment/6af15786bf36fdf837b4885b)

Replay also needs a consistency boundary across the agreed tables. An open-orders contract and a stock-balance contract can each return valid read-only results while observing different points in a replicated transaction, producing an inconsistent combined answer.

I would expose the replica snapshot or replication watermark used for the response, and test an order update whose related inventory change arrives separately. That would establish whether the Bridge sees a coherent business state or merely individually valid rows. Separating the operational database from agent load is useful, but the replica's transaction visibility becomes part of the tool contract too.