Scoping and securing secrets for workflows or workspace bootstrapping

I’m new to Replit, but am trying to set up a workflow where it could run an existing app and download or refresh a development database snapshot from a remote environment.

Goal: Secrets for onBoot or workflow or one-time script. Not accessible by AI agent or at app runtime. The idea is similar to Codex cloud env setup, where there can be secrets that are isolated for setup, but not available after.

Problem?: It looks secrets stored at the account or app level would be available in the env, at runtime, and to the AI agent. I want to scope this to a specific setup or manually initiated process.

Is this essentially impossible and just a feature request for now?

Example: Imagine I start a Rails app and Postgres database, but then want to use a limited-access Google Service Account key to securely download a snapshot of the database from a Google Cloud Storage bucket and load it into the database either on initial boot, or on-demand by user request or workflow (to refresh the latest data for testing).