Over my dead body. If another sysadmin or an engineer asks me to poke a single pinhole to a single IP, we have a discussion about the implications. More often than not, we can avoid that whole mentality and pull rather than push from the server in question. If I got such a request from an outside source, you can bet the scrutiny over the issue would be 10x more intense. In a situation where somebody was to fall for something like this hook, line and sinker, I'd argue such a person shouldn't have administrative access to things like corporate firewalls in the first place.
On the other hand, in my younger days I was a network engineer. I ran into more than a few networks of huge multinationals that were designed about as poorly as you could imagine. Oh they had expensive hardware, and plenty of engineers who loved to sign their correspondence with the usual alphabet soup following their name and title. But you can only explain how a static route works to a corporate network admin so many times before you start becoming cynical about the whole thing. I can easily imagine one of those guys opening up an IP range willy-nilly on a firewall, and not realizing it until long after the damage was done. You might be surprised how often this kind of thing happens.
