0% 0% 0% 0%

Secret Manager

Index
  1. 01. Concepts
  2. 02. Architecture
  3. 03. State & Storage
  4. 04. Tools
  5. 05. BigQuery
  6. 06. Cloud Storage
  7. 07. Compute & Containers
  8. 08. Cloud Run
  9. 09. Pub/Sub
  10. 10. Databases
  11. 11. Observability
  12. 12. Access & Billing
  13. 13. Secret Manager
  14. 14. Networking
  15. 15. Scheduling & Tasks
  16. 16. Build & Artifacts
  17. 17. Guardrails
  18. 18. Setup
  19. 19. Deploy to Cloud Run

Secret Manager

One rule governs this page: a secret’s value never leaves Google Cloud. enoki reads Secret Manager metadata only — names, versions, and their state — so you can audit and locate secrets from Slack without ever exposing their contents.

Reads — metadata only

  • list_secrets(project_id) — the secret names in a project. No values.
  • list_secret_versions(secret_id, project_id) — the versions of a secret and each one’s state (enabled, disabled, destroyed). No values.

Why there is no “read secret” tool

There is deliberately no tool that calls access_secret_version — the API that returns the actual secret material. A chat surface is exactly the wrong place for a plaintext credential: it would land in Slack, in thread history, and in an LLM’s context window. enoki can tell you a secret exists, how many versions it has, and whether they’re active — the questions you can safely answer in a thread — and stops there. See Guardrails.

Next: Networking.