Some people consider the MAC address to be "somewhat secret". This is misguided, but be aware that making the MAC addresses public may generate some amount of nervousness. You may have to justify yourself.
For instance, a rather common configuration option on "intelligent switches" is to restrict each ethernet port to a single MAC or only a short list of MAC addresses; this is an attempt to discourage employees from bringing their own device. It is not a strong security system; it can be easily countered by setting the MAC address of an external device to a specific value. However, this has contributed to propagate the idea that the MAC address is a kind of password, hence the nervousness about publication.
Wake on LAN is in a similar situation: since it allows for waking machines up remotely, it could, potentially, be used by an attacker to attack powered-off machines. In that respect, switching the machine off no longer is the ultimate security.
(It can make for an interesting DoS. A computer which boots up uses more power than a computer which is merely "up"; this effects last for only a few seconds, until all hard disks are up to speed and the CPU has finished its boot-time self tests. With a generic Wake-on-LAN, it is possible to wake a bunch of machines simultaneously, and overload the fuses. I have known a computer room which could handle all systems up and running, but not all systems booting. So the machines had to be configured to not power-up automatically when power is back after a shortage. A generalized Wake-on-LAN may allow for the same kind of effect.)