Tools

Every capability enoki has is an enumerated, typed tool — there is no free-form command surface. Read tools run immediately under your Google identity; write tools pause for a one-click approval in Slack before anything happens. When your account isn’t connected, a tool returns a “connect first” message instead of failing.

enoki ships seventy-plus tools across the GCP surface below. Each service has its own page with the exact tool list, arguments, and which calls are writes.

By service

• BigQuery — datasets, schema, dry-run cost preview, cost-guarded SELECT, exports, job history, and dataset create/delete.
• Cloud Storage — list buckets and objects; create/delete buckets.
• Compute & Containers — Compute Engine instances (start, stop, resize, snapshot), GKE reads, and Cloud Functions reads.
• Cloud Run — service and revision reads, plus approval-gated rollback and traffic split.
• Pub/Sub — topics and subscriptions: list, create, delete.
• Databases — Cloud SQL, Cloud Spanner, and Memorystore (Redis) reads.
• Observability — Cloud Monitoring alert policies and recent Cloud Logging entries (read).
• Access & Billing — projects, IAM policy (with approval-gated grant/revoke), service-account key hygiene, access search, audit logs, and billing (read).
• Secret Manager — secret and version metadata (values never leave GCP).
• Networking — VPC networks, firewall rules, and Cloud DNS (read).
• Scheduling & Tasks — Cloud Scheduler (pause/resume/run) and Cloud Tasks queues (read).
• Build & Artifacts — Cloud Build (with approval-gated retry) and Artifact Registry (with version cleanup).

Delivery

Some tools produce a report or an export (for example a BigQuery result set). enoki hands it back as a Slack file — deliver_report(fmt, filename) renders the current report as a pdf or txt and uploads it to the thread. Nothing is written to disk in your project; the file is delivered and forgotten.

What’s deliberately still read-only

enoki now writes IAM role bindings (grant/revoke), but only through a narrow, plan-bound, approval-gated path — see Access & Billing. Some things stay read-only on purpose:

• Billing — no tool changes a billing account or budget; the blast radius is too high for a single Approve/Deny.
• Secret values — enoki reads secret metadata, never the secret material. See Secret Manager.
• Container rollouts beyond traffic — enoki can re-point Cloud Run traffic, but never builds, deploys, or deletes revisions.

These are deliberate omissions, not oversights. See Guardrails.

Next: BigQuery — the first service, end to end.