AIops-tools/Nutanix-AIops

> **Disclaimer**: Community-maintained open-source project. **Not affiliated with, endorsed by, or sponsored by Nutanix.** Product and trademark names belong to their owners. MIT licensed.
Governed AI-ops for **Nutanix Prism Central** (v4 REST API) — clusters, hosts,
VMs (AHV + ESXi), storage, network, catalog, data protection / DR, alerts, LCM
upgrades, and capacity — with a **built-in governance harness**: unified audit
log, token/runaway budget guard, undo-token recording, and descriptive
risk-tier labels. Connects to Prism Central on HTTPS :9440 with
HTTP Basic auth (username + encrypted password). Self-contained: no dependencies
beyond httpx and the MCP SDK.
Why this over a read-only Nutanix MCP
- **Automatic ETag / If-Match** on every mutation. The v4 API rejects an update
or delete without the entity's current ETag — the classic footgun. This tool
fetches and sends If-Match for you.
- **Automatic pagination** — list tools walk every v4 page for you, and return a
{" ": [...], "returned", "limit", "truncated"} envelope so a capped
read announces itself instead of looking like the whole estate.
- **Absent is not empty** — a field Prism Central did not return comes back as
null, never as "". v4 omits a lot of fields; the two facts stay distinct.
- **Mixed-hypervisor VM listing** — vm_list returns both **AHV** and **ESXi**
guests under the same Prism Central (built for hypervisor-migration estates).
- **Governance harness** — audit / token+call budget / descriptive risk-tier
labels / undo-token / prompt-injection sanitize, with **dry-run +
double-confirm** on destructive writes.
What this tool does, and does not, decide
It delivers Nutanix Prism Central operations — reads and writes — accurately and
efficiently, and records every one of them. It does **not** decide whether a write is
allowed to happen. That is the agent's judgement, or the permission of the account
you connect it with: connect with a Prism Central account holding only a
read-only (Viewer) role, and the writes fail at the server — the place that
actually owns the permission.
So there is no read-only switch, no policy file, no approval gate to configure. The
one thing the tool guarantees is that nothing is silent: **every call, over MCP and
over the CLI alike, lands an audit row** in ~/.nutanix-aiops/audit.db, and
destructive writes still capture their before-state and record an inverse where one
exists.
> Each tool declares a risk_level, carried into the audit row as a descriptive
> tier (none/confirm/review) — so a reviewer can see at a glance that a row was a
> high-risk delete. It is a label, not a gate.
Running a smaller / local model? See
agent-guardrails.md — it lists
the guardrails this tool now enforces for you (so you don't spend prompt budget
restating them) and gives a ready-made system prompt for what's left.
Capability matrix (51 MCP tools)
| Group | Tools | Count | R/W |
|-------|-------|:-----:|:---:|
| **Clusters** | cluster_list, cluster_health, host_list, cluster_utilization | 4 | 4 read |
| **VMs** | vm_list, vm_get, vm_power_on, vm_guest_shutdown, vm_power_off, vm_reboot, vm_create, vm_update, vm_clone, vm_delete, vm_migrate | 11 | 2 read · 9 write |
| **Storage** | storage_container_list / _create / _update / _delete | 4 | 1 read · 3 write |
| **Network** | subnet_list, subnet_get, subnet_create, subnet_delete | 4 | 2 read · 2 write |
| **Catalog** | image_list, image_delete, category_list, category_create, category_assign | 5 | 2 read · 3 write |
| **Data protection / DR** | snapshot_list / _create / _delete / _restore, recovery_point_list, protection_domain_list, vm_protect, pd_failover | 8 | 3 read · 5 write |