The org's stored secrets, names only (values are never shown)

Your org's stored secrets, BY NAME ONLY - values are sealed on arrival and never shown to you or anyone: there is nothing here to paste anywhere. Returns [{name, created_at, last_used_at}]. Reference one as an env value in run_command or submit_job: env: {WANDB_API_KEY: {secret: "wandb-prod"}} - the platform resolves it at launch and the value never appears in this chat. Honest limits, stated plainly: a stored secret still enters the container's environment, so code running there can read it or print it; for reading private datasets prefer a connection (list_connections) - there the credential never enters the container at all. Missing the secret you need? A human org admin adds one from their own terminal or CI - autor secret create - and NEVER pastes a token, key, or password into this chat (transcripts are recorded and outlive the task). Secret mutations are not callable over MCP. Org secrets are org-wide: a vended workspace token (the per-tenant credential) can neither list nor reference them.