Fly proxy binds to public port, risk of data exposure

fly proxy binds to both 127.0.0.1 and 0.0.0.0. Tested on WSL2 Ubuntu Jammy Jellyfish. On public networks, this may result in unintentional data exposure. It would be better if we can use the following syntax fly proxy <user's host>:<user's port>:<remote port> similar to docker. By default fly proxy should only bind to 127.0.0.1 and allow the tunnel to be exposed to the public using fly proxy 0.0.0.0:5432:5432 -a <postgres or whatever app name> if the need arises.