I downloaded the ivman source myself and I guess that the halmount is a wrapper around the commands supplied by ivman. It may be suse specific.
If you download the SuSE rpm package, you can use "mc" to extract the halmount.py script. The /usr/bin/halmount command is simply a symbolic link to /usr/bin/halmount.py.
The rest of the source package is a tarball of the ivman package. There should be plenty there to study. Maybe you will write your own wrapper for the ivman commands to do what you want, or simply craft the xml rules.
You can also use:
rpm2cpio ivman-0.6.14-72.src.rpm >ivman-0.6.14-72.cpio
cpio -vid < ivman-0.6.14-72.cpio
to extract the files from the rpm.
There is also a halmount.1 man page. However, be sure to study the script before using it. The xml files used by ivman or hal may differ between my setup and yours. HAL works hand in hand with udevinfo when a device is added. Your system may be configured differently. This script uses the label of a filesystem, and udev creates a /dev/disk/by-label/<label> symbolic shortcut to the actual device. The rules for it to do this are in /etc/udev/rules.d/. Your system may not do this as its configured.
Another thing to look at is your system uses the PolicyKit package which may control whether a regular user using a desktop manager can mount a device. The policy kit distinguishes between a user using the desktop or one ssh'ing into the computer and may allow or deny an action accordingly. ( some documentation in /usr/share/doc/policykit/spec/polkit-spec.html if it's installed )
I know this is a lot to digest. I wish there was better documentation on dbus, hal, udev & policy kit and how it all fits together.