Files

T

justinandClaude Opus 5 e5f05eff6c feat(catalog): cover Windows guest-mutating tools in the starter list

The catalog is opt-in: an unlisted tool passes through unguarded. The
shipped starter list was ssh/exec and ansible/run_playbook, both Linux
shaped, so an agent changing a protected Windows guest over WinRM or
PowerShell was never guarded at all. That does not fail loudly, it
simply never inserts a checkpoint.

Adds winrm/run_command, winrm/run_ps, powershell/invoke_command and
smb/write_file. The smb entry is there because a file written into a
share changes the guest without any shell being involved.

Test asserts the example config covers both platforms and that every
entry names a vm_arg, since without one the guard cannot resolve a VM.

Still illustrative, not exhaustive: tool names vary per MCP server, so
users add their own with zerto_add_mutating_tool. That reactive model is
the real weakness here and is worth revisiting separately.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_016yVfC5nvZowoLFnEGWhLGn

2026-09-21 14:32:52 -04:00

2.9 KiB

Raw Blame History

zerto-ai-rewind

PoC MCP that makes an agent pin a Zerto tagged checkpoint before it changes a VM, then pull a file back from that tag.

If the loop works, these tools are the delta to add to official ZVM MCP (ZVM.MCP, 10.9). This repo is one MCP process for the demo. It is not a second full ZVM catalog.

What it does

zerto_find_protection — VM name, hostname, or vmIdentifier to exactly one VM and every VPG. Zero or two-plus VMs: stop.
zerto_create_tagged_checkpoint / zerto_guard_before_mutate — same tag on every protecting VPG, wait until listed. The name records which agent and what it is doing: ai:<agent> | <action> | vm=<vm> | change=<id> | <utc>.
zerto_recover_file — FLR after a human sets confirmed=true. Linux and Windows guest paths. Locally replicated VPGs only: FLR runs at the VPG's recovery site. Reports its own unmount; zerto_list_flr_sessions / zerto_end_flr_session find and reap a mount orphaned by a crashed recovery.
Mutating catalog — opt-in list of MCP tools that must be guarded. Unlisted tools pass through. Users add entries. The starter list covers Linux (ssh, ansible) and Windows (winrm, powershell, smb), and is illustrative, not exhaustive.

Official ZVM MCP already has inventory and failover test. It does not insert tagged checkpoints or run FLR.

Setup

Python 3.12+.

python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
cp config.example.json config.json
# edit zerto_url, username, password

Keycloak password-grant, client_id zerto-client on 10.x. Appliance certs are self-signed; verify_tls defaults to false.

stdio MCP (Claude Desktop, VS Code, Cursor, OpenCode):

{
  "mcpServers": {
    "zerto-rewind": {
      "command": "zerto-rewind-mcp",
      "env": {
        "ZERTO_REWIND_CONFIG": "/absolute/path/to/config.json"
      }
    }
  }
}

Copy skills/zerto-rewind/SKILL.md into the client's skill path.

pytest

Demo

Protected app VM. Agent is about to edit a guest config file.

Guard: discover VPG set, insert tagged checkpoint, wait.
Agent writes the bad config.
Human confirms.
zerto_recover_file from that tag.

Git never had the file. RPO is the journal, not last night's backup.

Certified for this PoC

vSphere ZVM 10.x and ZCA on AWS/Azure, same REST paths. HVM is out (separate swagger). Failover Live is not a tool.

Tagged checkpoints cannot be inserted when the protected site is Azure or AWS (Zerto API). Point this server at the vSphere protected ZVM.

Not this product

Moholo Agent Rewind snapshots the agent's laptop tools. This server uses the Zerto journal as the snapshot store. Do not copy their file blobs.

Upstream

Ask Zerto engineering to add to ZVM.MCP: find-by-unique-VM-with-all-VPGs, tagged checkpoint insert that waits, FLR. Keep VPG settings CRUD where it already is.

2.9 KiB Raw Blame History