No, because as soon as the restore has started the files it's using get written over. You can kill it at any point, but the database being restored over will already be gone at that time and you'd need to restart a restore to get the DB back
Maybe take away his sysadmin permissions, limit to other permissions to do what he needs and stress the importance of being really, really careful. Or make the normal login that the guys use a non-sysadmin so that they have to change login to do anything sensitive
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability