0% 0% 0% 0%

Databases

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

Databases

Cloud SQL

  • list_cloudsql_instances(project_id) — the Cloud SQL instances in a project, each with its database version, state, and region.

Cloud SQL has no typed Google client library, so this tool goes through the SQL Admin discovery API under your own identity — the same per-user boundary as every other tool.

It is read-only by design. Instance creation, deletion, and configuration changes have a large blast radius and belong behind dedicated, resource-level guardrails rather than a generic approval button — so they’re deliberately absent, in the same spirit as the missing IAM and billing writes. See Guardrails.

Cloud Spanner

  • list_spanner_instances(project_id) — the Spanner instances in a project, each with its config, capacity (nodes or processing units), and state.
  • list_spanner_databases(instance, project_id) — the databases in an instance, with their state.

Memorystore (Redis)

  • list_redis_instances(project_id) — the Memorystore for Redis instances across every region, each with its tier, memory size, and state.

Spanner and Memorystore are read-only here for the same reason as Cloud SQL — provisioning and scaling a managed database is too consequential for a generic Approve/Deny.

Next: Observability.