The AnyConnect client doesn't have a CLI. It does use some profiles (.xml files) that govern its behavior when launched.
The "server" is typically an ASA. You can configure just about everything from either ASA CLI or the GUI (ASDM). That includes actions which will result in the creation of the client xml files (which can either be set to download upon client connection or pre-deployed).
The only command line that I know of is to use the vpncli.exe - but that is only to connect. As Marvin said, you can configure the XML files (either on the ASA, or manually edit them on your machine) but there is no 'command line' on the anyconnect client.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...