All the developers have access to the machine that CU uses due to the Developer Server being hosted on the same machine, we rarely make our presence known to CU's administrators that have access. I myself have observed the server a couple times under Michael's instruction to watch the server after he had an unexpected occurance that took a couple of days. I've only had to ban someone for a couple hours for mass joining on different accounts on the same IP and attempting to spam. We try to give many chances, and not perma ban on the first offense. That was only a rare case I would ban someone for that long, usually its just 20 minutes or a kick.
No DCE Developers (Besides myself) have touched CU's console, and I have the log displaying the information of whoever connects to the teamviewer on a separate monitor, so its safe to say that nobody has abused the system. All of our developers and Administrators are trustworthy when it comes to responsibility, at least for my side of the development team
Michael has the troubled side of developers, but about half of them are trustable and know proper displine procedures, while the other half are not familar with banning procedures as of right now due to them being nearly constant at work or taking a break.
Michael has previously said that if any disaster strikes the server, the DCE Developers will be the first people to be deployed and here is why: Coding the client takes alot more dedication then making an addon, and the chance that the client developers will be ready to deploy is slim. .