If you really, absolutely cannot install any Perl modules, your options are significantly more limited. I'm just going to take your word for it and assume that the "other, more complicated reasons" you mention for not being able to install modules are related to your boss's life-threatening CPAN allergies or something equally dire, which are not resolved by installing locally. Here are a couple of (less than ideal) options:
- (Best option) Get your sys admin to set up ssh keys so you don't need to enter a password to connect to your remote host. Really you should do this even if you can use Perl modules.
- Use an expect script to send your password. This, of course, requires expect to be installed, which like option #1 may require a visit to your sys admin accompanied by a modicum of grovelling and/or bribery. If you go this route, here is a good tutorial (on expect, not on grovelling). But honestly, if all you're using expect for is to send your ssh password, you are introducing a lot of unnecessary complication that could be easily taken care of by setting up ssh keys (see option #1).
Notice that both options may require you to ask your sys admin for help. If he/she is already going to install/configure something, you might as well ask them to install some Perl modules (Expect.pm and Net::SSH2) for you while they're at it (unless, of course, somebody could die or become horribly disfigured as a result).