vmx-aps - APS command line wrapper

vmx-aps is a command-line utility for interacting with the XTD Guardsquare API. It simplifies operations like uploading apps, checking versions, and managing protections using a simple CLI.

---

What's new in 3.0.4

• Added "/v1" prefix to the API that retrieves the default analytics agent configuration

Note: The full changelog is included in the distribution (CHANGELOG.md).

---

🛠️ Installation

$ pipenv shell
$ pip install vmx-aps

---

🚀 Usage

All commands require an API key file (JSON format) obtained from the XTD portal -> Settings -> API Key Manager.

$ vmx-aps --api-key-file ~/Downloads/api-key.json <command> [args...]

Example:

$ vmx-aps --api-key-file ~/Downloads/api-key.json get_version
{
  "apkdefender": {
    "preanalysis-defaults": "20250401.json",
    "raven-apkdefender": "v4.8.3_20250401",
    "raven-template": "20250401.json",
    "sail": "1.46.4",
    "version": "4.8.3"
  },
  "apsdefenders": "2025.12.3-prod",
  "iosdefender": {
    "sail": "1.46.4",
    "version": "7.2.1"
  },
  "version": "2025.12.0-prod"
}

---

🔐 Authentication

All requests are authenticated via an API key in a local JSON file. The file must contain:

{
  "appClientId": "your-app-client-id",
  "appClientSecret": "your-app-client-secret",
  "encodedKey": "your-encoded-key"
}

The CLI tool reads only the value of encodedKey. You can also pass that value as an argument directly using --api-key or -a:

$ vmx-aps -a "your-encoded-key" get_version
{
  "apkdefender": {
    "preanalysis-defaults": "20250401.json",
    "raven-apkdefender": "v4.8.3_20250401",
    "raven-template": "20250401.json",
    "sail": "1.46.4",
    "version": "4.8.3"
  },
  "apsdefenders": "2025.12.3-prod",
  "iosdefender": {
    "sail": "1.46.4",
    "version": "7.2.1"
  },
  "version": "2025.12.0-prod"
}

---

📚 Available Commands

protect

Performs app protection on a given mobile app binary (Android or iOS). This is a high-level command that uploads an app, runs protection, waits for completion, and downloads the protected binary.

⚠️ This process may take several minutes to complete.

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect --file path/to/app.apk

🔧 Options

• --file (required)
  Path to the input binary. Supported formats:

  • Android: .apk, .aab
  • iOS: zipped .xcarchive folder

• --subscription-type (optional)
  Specifies the subscription type.
  Choices: ["APPSHIELD_PLATFORM", "COUNTERSPY_PLATFORM", "XTD_PLATFORM"]

• --signing-certificate (optional see NOTE)
  Path to a PEM-encoded signing certificate file, used for Android signature verification or certificate pinning.
  NOTE: this is mandatory for Android protection.

• --secondary-signing-certificate (optional)
  Path to a PEM-encoded secondary signing certificate file, used for Android signature verification or certificate pinning.

• --mapping-file (optional)
  Path to the Android R8/ProGuard mapping file for symbol preservation during obfuscation.

• --build-protection-configuration (optional)
  Path to the build protection configuration JSON file.

• --build-certificate-pinning-configuration (optional)
  Path to the JSON file with the build certificate pinning configuration.

• --build-configuration (optional see NOTE)
  Path to the JSON file with XTD configurations.
  NOTE: Only for Android protection.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect \
  --file ~/test-app.apk \
  --subscription-type XTD_PLATFORM \
  --signing-certificate ~/cert.pem \
  --secondary-signing-certificate ~/secondary-cert.pem \
  --mapping-file ~/proguard.map \
  --build-protection-configuration ~/buildProtConfig.json \
  --build-certificate-pinning-configuration ~/certPinningConfig.json \
  --build-configuration ~/xtd-conf.json

---

list-applications

Lists applications associated with your XTD account. You can filter the results by application ID, group, or subscription type.

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-applications

🔧 Options

• --application-id (optional)
  If provided, returns details for a specific application matching the given ID.

• --group (optional)
  Filters applications to those belonging to the specified group.

• --subscription-type (optional)
  Specifies the subscription type.
  Choices: ["APPSHIELD_PLATFORM", "COUNTERSPY_PLATFORM", "XTD_PLATFORM"]

✅ Examples

List all applications:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-applications

List a specific application:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-applications --application-id c034f8be-b41d-4799-ab3b-e96f2e60c2ae

List applications from a group:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-applications --group my-group

List applications with a specific subscription type:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-applications --subscription-type XTD_PLATFORM

---

add-application

Registers a new application with your XTD account. You must specify the platform, application name, and package ID. You can also set access restrictions and grouping options.

$ vmx-aps --api-key-file ~/Downloads/api-key.json add-application --os android --name "My App" --package-id com.example.myapp

🔧 Options

• --os (required)
  Target operating system.
  Choices: android, ios

• --name (required)
  Friendly display name for the application.

• --package-id (required)
  The app's unique package ID (e.g., com.example.myapp).

• --group (optional)
  Application group identifier, useful for managing related apps.

• --subscription-type (optional)
  Specifies the subscription type.
  Choices: ["APPSHIELD_PLATFORM", "COUNTERSPY_PLATFORM", "XTD_PLATFORM"]

• --private (optional)
  Restrict visibility and access to this app. Implies both --no-upload and --no-delete.

• --no-upload (optional)
  Prevent other users from uploading new versions of this app.

• --no-delete (optional)
  Prevent other users from deleting builds of this app.

✅ Examples

Add a public Android app:

$ vmx-aps --api-key-file ~/Downloads/api-key.json add-application \
  --os android \
  --name "My App" \
  --package-id com.example.myapp

Add a private iOS app to a group:

$ vmx-aps --api-key-file ~/Downloads/api-key.json add-application \
  --os ios \
  --name "iOS Secure App" \
  --package-id com.example.iosapp \
  --group enterprise-apps \
  --private

---

update-application

Updates the properties of an existing application registered in your XTD account. You can change the app's name and its access permissions.

$ vmx-aps --api-key-file ~/Downloads/api-key.json update-application --application-id 12345 --name "New App Name"

🔧 Options

• --application-id (required)
  ID of the application to be updated. This value cannot be changed.

• --name (required)
  New friendly name for the application.

• --private (optional)
  Restrict the application from being visible to other users. Implies --no-upload and --no-delete.

• --no-upload (optional)
  Prevent other users from uploading new builds for this app.

• --no-delete (optional)
  Prevent other users from deleting builds for this app.

✅ Examples

Update app name:

$ vmx-aps --api-key-file ~/Downloads/api-key.json update-application \
  --application-id 12345 \
  --name "My Renamed App"

Update app name and make it private:

$ vmx-aps --api-key-file ~/Downloads/api-key.json update-application \
  --application-id 12345 \
  --name "Secure App" \
  --private

---

delete-application

Deletes an application from your XTD account, including all associated builds. This operation is irreversible.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-application --application-id 12345

🔧 Options

• --application-id (required)
  The ID of the application you want to delete.

⚠️ Warning

This operation will permanently delete:

• The application record
• All uploaded builds for the application

Make sure you have backups or exports of important data before running this command.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-application --application-id 12345

---

set-signing-certificate

Sets the signing certificate for a specific Android application. The certificate must be in PEM format.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-signing-certificate --application-id 12345 --file cert.pem

🔧 Options

• --application-id (required)
  The ID of the application to update.

• --file (required)
  Path to the PEM-encoded Android certificate file.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-signing-certificate \
  --application-id 12345 \
  --file ~/certs/my-cert.pem

---

delete-signing-certificate

Deletes the signing certificate for a specific Android application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-signing-certificate --application-id 12345

🔧 Options

• --application-id (required)
  The ID of the application to update.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-signing-certificate \
  --application-id 12345

---

set-secondary-signing-certificate

Sets the secondary signing certificate for a specific Android application. The certificate must be in PEM format.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-secondary-signing-certificate --application-id 12345 --file secondary-cert.pem

🔧 Options

• --application-id (required)
  The ID of the application to update.

• --file (required)
  Path to the PEM-encoded Android (secondary) certificate file.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-secondary-signing-certificate \
  --application-id 12345 \
  --file ~/certs/my-secondary-cert.pem

---

delete-secondary-signing-certificate

Deletes the secondary signing certificate for a specific Android application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-secondary-signing-certificate --application-id 12345

🔧 Options

• --application-id (required)
  The ID of the application to update.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-secondary-signing-certificate \
  --application-id 12345

---

set-mapping-file

Associates an R8/ProGuard mapping file with a specific Android build. This improves symbol readability and debugging of protected builds.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-mapping-file --build-id 98765 --file proguard.map

🔧 Options

• --build-id (required)
  ID of the Android build to associate the mapping file with.

• --file (required)
  Path to the R8/ProGuard mapping file.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-mapping-file \
  --build-id 98765 \
  --file ~/builds/proguard.map

---

set-protection-configuration

Sets the protection configuration for an application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-protection-configuration --application-id 12345 --file protConfig.json

🔧 Options

• --application-id (required)
  The ID of the application to update.

• --file (required)
  Path to the protection configuration JSON file.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-protection-configuration \
  --application-id 12345 \
  --file ~/protConfig.json

---

delete-protection-configuration

Deletes the protection configuration for an application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-protection-configuration --application-id 12345

🔧 Options

• --application-id (required)
  The ID of the application to update.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-protection-configuration \
  --application-id 12345

---

set-[application|build]-configuration

Sets the XTD configuration for application or build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-application-configuration --application-id 12345 --file xtd-config.json
or
$ vmx-aps --api-key-file ~/Downloads/api-key.json set-build-configuration --build-id 12345 --file xtd-config.json

🔧 Options

• --application-id (required) if using set-application-configuration The ID of the application to update.

• --build-id (required) if using set-build-configuration The ID of the build to update.

• --file (required)
  Path to the JSON file with the pinned certificate(s).

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-application-configuration \
  --application-id 12345 \
  --file ~/certPinningConfig.json

---

get-[application|build]-configuration

Fetch the XTD configuration for application or build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-application-configuration --application-id 12345
or
$ vmx-aps --api-key-file ~/Downloads/api-key.json get-build-configuration --build-id 12345

🔧 Options

• --application-id (required) if using get-application-configuration The ID of the application to query.

• --build-id (required) if using get-build-configuration The ID of the build to query.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-application-configuration \
  --application-id 12345

---

delete-[application|build]-configuration

Delete the XTD configuration for application or build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-application-configuration --application-id 12345
or
$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build-configuration --build-id 12345

🔧 Options

• --application-id (required) if using get-application-configuration The ID of the application to query.

• --build-id (required) if using get-build-configuration The ID of the build to query.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build-configuration \
  --build-id 12345

---

set-certificate-pinning-configuration

Sets the certificate pinning configuration for an application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-certificate-pinning-configuration --application-id 12345 --file certPinningConfig.json

🔧 Options

• --application-id (required)
  The ID of the application to update.

• --file (required)
  Path to the JSON file with the pinned certificate(s).

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-certificate-pinning-configuration \
  --application-id 12345 \
  --file ~/certPinningConfig.json

---

delete-certificate-pinning-configuration

Deletes the certificate pinning configuration for an application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-certificate-pinning-configuration --application-id 12345

🔧 Options

• --application-id (required)
  The ID of the application to update.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-certificate-pinning-configuration \
  --application-id 12345

---

get-certificate-pinning-configuration

Gets the certificate pinning configuration for an application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-certificate-pinning-configuration --application-id 12345

🔧 Options

• --application-id (required)
  The ID of the application to retrieve.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-certificate-pinning-configuration \
  --application-id 12345

---

set-build-certificate-pinning-configuration

Sets the certificate pinning configuration for a build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-build-certificate-pinning-configuration --build-id 12345 --file certPinningConfig.json

🔧 Options

• --build-id (required)
  The ID of the build to update.

• --file (required)
  Path to the JSON file with the pinned certificate(s).

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-build-certificate-pinning-configuration \
  --build-id 12345 \
  --file ~/certPinningConfig.json

---

delete-build-certificate-pinning-configuration

Deletes the certificate pinning configuration for a build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build-certificate-pinning-configuration --build-id 12345

🔧 Options

• --build-id (required)
  The ID of the build to update.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build-certificate-pinning-configuration \
  --build-id 12345

---

get-certificate-pinning-configuration

Gets the certificate pinning configuration for a build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-build-certificate-pinning-configuration --build-id 12345

🔧 Options

• --build-id (required)
  The ID of the build to retrieve.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-build-certificate-pinning-configuration \
  --build-id 12345

---

list-builds

Lists build artifacts associated with applications in your XTD account. You can filter builds by application ID, build ID, or subscription type.

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-builds

🔧 Options

• --application-id (optional)
  Returns builds associated with the given application.

• --build-id (optional)
  Returns a single build identified by this build ID.

• --subscription-type (optional)
  Specifies the subscription type.
  Choices: ["APPSHIELD_PLATFORM", "COUNTERSPY_PLATFORM", "XTD_PLATFORM"]

✅ Examples

List all builds:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-builds

List builds for a specific application:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-builds --application-id 12345

Get a specific build by ID:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-builds --build-id 98765

Filter builds by subscription:

$ vmx-aps --api-key-file ~/Downloads/api-key.json list-builds --subscription-type XTD_PLATFORM

---

add-build

Uploads a new mobile app build (Android .apk or iOS .xcarchive) to a registered application in your XTD account.

$ vmx-aps --api-key-file ~/Downloads/api-key.json add-build --application-id 12345 --file path/to/app.apk

🔧 Options

• --application-id (required)
  The ID of the application the build belongs to.

• --file (required) Path to the build file. Supported formats:

  • Android: .apk
  • iOS: zipped .xcarchive folder

• --subscription-type (optional)
  Specifies the subscription type.
  Choices: ["APPSHIELD_PLATFORM", "COUNTERSPY_PLATFORM", "XTD_PLATFORM"]

✅ Examples

Upload an Android build:

$ vmx-aps --api-key-file ~/Downloads/api-key.json add-build \
  --application-id 12345 \
  --file ~/apps/my-app.apk

Upload an iOS build with subscription tier:

$ vmx-aps --api-key-file ~/Downloads/api-key.json add-build \
  --application-id 12345 \
  --file ~/apps/my-ios-app.xcarchive.zip \
  --subscription-type XTD_PLATFORM

---

delete-build

Deletes a specific build from your XTD account. This action is irreversible and will remove the associated protected binary.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build --build-id 98765

🔧 Options

• --build-id (required)
  The ID of the build you want to delete.

⚠️ Warning

This command will permanently delete the specified build, including any associated protection artifacts.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build --build-id 98765

---

set-build-protection-configuration

Sets the protection configuration for a build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-build-protection-configuration --build-id 12345 --file protConfig.json

🔧 Options

• --build-id (required)
  The ID of the build to update.

• --file (required)
  Path to the build protection configuration JSON file.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json set-build-protection-configuration \
  --build-id 12345 \
  --file ~/protConfig.json

---

delete-build-protection-configuration

Deletes the protection configuration for a build.

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build-protection-configuration --build-id 12345

🔧 Options

• --build-id (required)
  The ID of the build to update.

✅ Examples

$ vmx-aps --api-key-file ~/Downloads/api-key.json delete-build-protection-configuration \
  --build-id 12345

---

protect-start

Initiates the protection process for a build that was previously uploaded to your XTD account. This starts the backend protection job.

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-start --build-id 98765

🔧 Options

• --build-id (required)
  ID of the build to be protected.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-start --build-id 98765

Use protect-get-status to monitor the progress of this protection job after initiation.

---

protect-get-status

Retrieves the current status of a protection job for a specific build. This includes progress updates, completion, or failure states.

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-get-status --build-id 98765

🔧 Options

• --build-id (required)
  ID of the build whose protection status you want to check.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-get-status --build-id 98765

Use this command after starting a protection job with protect-start to monitor its progress.

---

protect-cancel

Cancels an ongoing protection job for a specific build in your XTD account. This can be used if the protection was started by mistake or is taking too long.

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-cancel --build-id 98765

🔧 Options

• --build-id (required)
  ID of the build whose protection job should be cancelled.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-cancel --build-id 98765

Use this command if you need to abort a protection job started with protect-start.

---

protect-download

Downloads a protected binary that was previously processed in your XTD account.

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-download --build-id 98765

🔧 Options

• --build-id (required)
  ID of the build whose protected output you want to download.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json protect-download --build-id 98765

Use this after confirming a successful protection job with protect-get-status.

---

get-account-info

Retrieves information about the current user and their associated organization (customer) from XTD.

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-account-info

🔧 Options

This command does not accept any additional arguments beyond the global --api-key-file.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-account-info

Returns details such as:

• Organization (customer) name and ID
• List of subscriptions
• User name and role

---

display-application-package-id

Extracts and displays the application package ID from an input file (APK or XCARCHIVE).
Useful when preparing to register an app using add-application.

$ vmx-aps --api-key-file ~/Downloads/api-key.json display-application-package-id --file path/to/app.apk

🔧 Options

• --file (required)
  Path to the input file:
  • Android: .apk
  • iOS: .xcarchive folder (typically zipped)

✅ Examples

Display package ID from an APK:

$ vmx-aps --api-key-file ~/Downloads/api-key.json display-application-package-id --file my-app.apk

Display package ID from an iOS XCARCHIVE:

$ vmx-aps --api-key-file ~/Downloads/api-key.json display-application-package-id --file my-ios-app.xcarchive.zip

---

get-sail-config

Retrieves the SAIL configuration for a specified platform and version.

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-sail-config --os android

🔧 Options

• --os (required)
  Operating system to retrieve the SAIL config for.
  Choices: android, ios

• --version (optional)
  Specific SAIL version to retrieve configuration for. If omitted, retrieves the latest available version.

✅ Examples

Get the latest SAIL config for Android:

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-sail-config --os android

Get a specific version of SAIL config for iOS:

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-sail-config --os ios --version 1.2.3

---

get-version

Retrieves the current version information for XTD services and components. This includes platform-specific defender versions, SAIL versions, and templates.

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-version

🔧 Options

This command does not take any additional options beyond the global --api-key-file.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-version

Example Output:

{
  "apkdefender": {
    "preanalysis-defaults": "20250401.json",
    "raven-apkdefender": "v4.8.3_20250401",
    "raven-template": "20250401.json",
    "sail": "1.46.4",
    "version": "4.8.3"
  },
  "apsdefenders": "2025.12.3-prod",
  "iosdefender": {
    "sail": "1.46.4",
    "version": "7.2.1"
  },
  "version": "2025.12.0-prod"
}

Use this command to verify deployed defender versions.

---

get-default-analytics-agent-configuration

Retrieves the default analytics agent configuration. If set, customer analytics agent configuration will be returned instead.

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-default-analytics-agent-configuration

🔧 Options

This command does not take any additional options beyond the global --api-key-file.

✅ Example

$ vmx-aps --api-key-file ~/Downloads/api-key.json get-default-analytics-agent-configuration

Example Output:

{
  "version": 1,
  "customResponses": {
    "detections": [
      {
        "type": "default",
        "responses": [
          {
            "type": "Report"
          },
          {
            "type": "Notify"
          },
          {
            "type": "SoftExit"
          }
        ]
      },
      {
        "type": "BootloaderDetected",
        "responses": [
          {
            "type": "Report"
          },
          {
            "type": "Notify"
          },
          {
            "type": "Popup",
            "message": "Bootloader detected! Error code: $E$"
          },
          {
            "type": "Sleep",
            "ms": 3000
          },
          {
            "type": "HardExit"
          }
        ]
      },
      {
        "type": "DebuggerDetected",
        "responses": [
          {
            "type": "Report"
          },
          {
            "type": "Notify"
          },
          {
            "type": "OpenUrl",
            "url": "https://www.verimatrix.com"
          },
          {
            "type": "SoftExit"
          }
        ]
      },
      {
        "type": "EmulatorDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      },
      {
        "type": "OverlayDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      },
      {
        "type": "RootingDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      },
      {
        "type": "SideLoadingDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      },
      {
        "type": "TamperingDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      },
      {
        "type": "HookingDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      },
      {
        "type": "MITMDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      },
      {
        "type": "VPNDetected",
        "responses": [
          {
            "type": "NOP"
          }
        ]
      }
    ]
  }
}

Use this command to retrieve the default analytics agent configuration.