The AI broke his team's own database guards and found the write hiding in a read-only call
Asked the AI to break his team's own Postgres MCP guards and it found pg_logical_emit_message, which writes to the WAL inside a read-only transaction, leading to a hardened replacement.
How it works
- He asks the AI to break the team's own database MCP guards
- It finds a function that writes to the log inside a read-only transaction
- Leading to hardening
Why it’s worth knowing
Read-only that writes is the kind of lie only an attacker finds. Theirs did.
Where it’s from
Summarized from a public post on news.ycombinator.com. See the original ↗