At this moment it's possible to run unit tests on a specific database and server configured in a runtime config. Running unit tests on Production (and sometimes even Acceptance) can be pretty tricky. If the unit test were to fail due to an transaction mismatch, the transaction might not be rolled back, which can result in serious data loss.
To prevent this from happening, maybe its an idea to define if running unit tests is allowed on a runtime config level. And off course make sure this is blocked when a developer triggers unit tests via this runtime config.