Inspect stored credentials during authentication debugging

Investigate credential and token state in your Android app using explicitly allowed secure-storage keys in local development.

SecureStorage tools help you investigate which credentials or tokens are stored when debugging authentication behavior. They can read, replace, or remove explicitly allowed values; keep access limited to the keys and local workflow you need.

Warning: Every tool in this suite is Critical because it can expose or mutate secrets. Keep the allow-list narrow and only enable this suite when you explicitly need secure-storage inspection or repair.

Install

Published artifact: ai.ansight:ansight-tools-securestorage-android.

dependencies {
    debugImplementation("ai.ansight:ansight-tools-securestorage-android:latest.release")
}

Register the Suite

import ai.ansight.runtime.AnsightOptions
import ai.ansight.tools.securestorage.withSecureStorageTools

val options = AnsightOptions.createBuilder()
    .withSecureStorageTools {
        withPreferencesName("secure_debug")
        allowKeyPrefix("debug.")
    }
    .withAllToolAccess()
    .build()

Registration API

withSecureStorageTools(...): registers the suite.
withPreferencesName(...): sets the secure-storage preferences name.
allowKey(...) / allowKeyPrefix(...): allow specific keys or key prefixes.

Specific Concerns

Values may contain credentials, tokens, or other secrets.
Keep key allow-lists narrow.
All secure-storage tools use Critical, including reads, and require withAllToolAccess() because their values are secrets.

Tool Matrix

Name	Id	Policy	Description
`Get Secure Storage Value`	`secure.get_value`	`Critical`	Reads a value from the configured secure storage backend.
`Set Secure Storage Value`	`secure.set_value`	`Critical`	Writes a secure-storage value.
`Remove Secure Storage Key`	`secure.remove_key`	`Critical`	Deletes a secure-storage key.

Tool Details

Use these tools only for explicit local debugging and repair workflows. Keep the key allow-list narrow.