Why does socket-proxy needs to know its own name for label allowlists?

[NotaInutilis]

Just for the sake of some "simple" curiosity: when setting up per container allowlists, the first step is to define a proxycontainername. Why is that necessary?

The only other tools that read configuration from docker labels are Traefik and Crowdsec, and both of those don't need to know their own container name. Is it a security measure like the 127.0.0.1 default listening address?

I'm rereading the docs again and found this: "In bridge network mode, each container that uses socket-proxy can be configured with its own allowlist." Might that be because that label behavior only applies to TCP listener/network mode and not Unix socket mode?