This is a terrible, terrible, terrible idea. You HAVE to be able to check the remotes no matter WHO wrote them or else you put your client, your computer, and everyone on your local network at risk to trojans.
Granted, I'm just commenting. But we're seeing more and more and more of these suggestions that, if implemented, would pose atrocious security risks to the computers that are running these scripts...
People joke about VBS being a "virus-builder script," but the truth is that both VBS and mIRC's scripts are already seriously vulnerable to these sorts of trojans, even without all of these other suggestions such as "give scripters acess to the windows registry and/or allow them to lock remote codes."
/remove, by itself, is one of the most potentially dangerous remote operations you could allow someone to use. When you start tacking on more and more methods of disguising this sorta stuff in mIRC, it becomes an even greater risk because you're practically asking hackers and other low-lives to try to exploit that stuff.
