Unable to start Mongo 3.4.24 as the Automation Agent is stopping it

We have a Mongo database that is NOT starting up - it appears that the Automation Agent is blocking Mongo from starting AND is removing some of the config files. What we see in the logs are the following:

[2022-04-05T04:46:07.802+0000] [.warn] [main/components/agent.go:LoadClusterConfig:236] [04:46:07.802] Will attempt to restore from local backup. : [04:46:07.802] Failed to parse https://stop-api-agents.mongodb.com/agents/api/automation/conf/v1/568f11c1e4b0479a196db693?av=11.11.0.7355&aos=linux&aa=x86_64&ab=64&ad=ubuntu1804&ah=prod-mongo2.nodes.sbaustralia.com&ahs=prod-mongo2.nodes.sbaustralia.com&at=1649133964714 as json : invalid character '<' looking for beginning of value
[2022-04-05T04:46:07.802+0000] [.info] [main/components/agent.go:LoadClusterConfig:246] [04:46:07.802] Attempting to restore cluster config from local backup...
[2022-04-05T04:46:07.802+0000] [.info] [src/config/config.go:ReadClusterConfig:419] [04:46:07.802] Retrieving cluster config from /var/lib/mongodb-mms-automation/mms-cluster-config-backup.json...
[2022-04-05T04:46:07.804+0000] [.info] [src/config/config.go:ReadClusterConfig:529] [04:46:07.804] Backing up cluster config to /var/lib/mongodb-mms-automation/mms-cluster-config-backup.json
[2022-04-05T04:46:07.804+0000] [.info] [main/components/agent.go:LoadClusterConfig:267] [04:46:07.804] New cluster config received! 0 (<nil>) -> 256 (<nil>)
[2022-04-05T04:46:07.804+0000] [.info] [src/modules/agents_unix.go:KillAllAgents:43] [04:46:07.804] Killing all running mongodb-mms-monitoring-agent agents at /var/lib/mongodb-mms-automation/mongodb-mms-monitoring-agent-.+\..+_.+/mongodb-mms-monitoring-agent *$
[2022-04-05T04:46:07.809+0000] [.info] [src/modules/agents_unix.go:KillAllAgents:43] [04:46:07.809] Killing all running mongodb-mms-backup-agent agents at /var/lib/mongodb-mms-automation/mongodb-mms-backup-agent-.+\..+_.+/mongodb-mms-backup-agent *$
[2022-04-05T04:46:07.905+0000] [.info] [main/components/agent.go:removeUnusedVersionsHelper:787] [04:46:07.905] Removing MongoDBBinary version = 3.4.24-865b4f6a96d0f5425e39a18337105f33e8db504d() from /var/lib/mongodb-mms-automation/mongodb-linux-x86_64-3.4.24 because it is no longer in the cluster config.
[2022-04-05T04:46:07.987+0000] [.info] [realtime/rtcollector/rtcollector.go:controlLoop:95] <rtCollector> [04:46:07.987] Received new cluster config version 256, edition <nil>!

Mongo is 3.4.24 and we know that it is out of date and we would like to upgrade to the latest Mongo version. Is there a way to get Mongo to start up WITHOUT the Automation Agent and then upgrade from there? How do we resurrect the config files for Mongo?