The potential customer rarely cares whether a service provider is running their business well. What matters is the product's value added and risks added, as compared to just using the underlying tech directly.
That's a big name for a slop fork. So many possibilities (with LLMs and without) but Google just can't bring themselves to do anything creative, let alone transformative.
There are no multi-statement queries in the binary protocol (where you get things like native cursors/pagination to efficiently iterate over result rows, and where you get the true parameter binding that is inherently robust against SQL injection.
It has a separate client to server packet that forces previous ones to complete as it will make otherwise-asynchronous (because pipelining) error reporting forcefully serial.
Other than this which is arguably not needed for queries that don't expect errors enough to need early/eager exception throwing during the course of a transaction, it's inherently naturally pipelined as you can just fire two or more statements worth of parameter binding and result fetching back-to-back without blocking on anything.
So? Go protect them the proper way. Do you want also to have all your messages scanned because you may be up to something illegal? Should we refrain from encryption because can help terrorists? That's not my cup of tea, I don't like proxy "protections" that are supposed to protect us from evil at some huge cost like loosing privacy or human connection.
I don't subscribe to the idea that we should ban knives because someone can use them to stab someone.
The meaning has changed very quickly for some reason, but I think the original meaning was that you evaluate the result in a superficial manner by checking if the program seems to work fine. So "vibe" here is as opposed to any methodical or formal approach. No code review etc.