A comment in source code. Not the discerning professional's preferred tool for guaranteeing security-critical behaviors to prevent "fire holes".
In the end, the only viable option is to forbid this behaviour, and document a rationale so nobody will enable it back again.
Perhaps they could make this warning bigger, but other than that...