AI and MCP
Turn an AI proposal into a controlled, verified operation
Every mutation is a time-limited request that a separately authorized person may approve or refuse.
Mutation tools
| Tools | Permission |
|---|---|
start_machine, shutdown_machine, pause_machine, resume_machine | power |
reset_machine, poweroff_machine | force |
create_snapshot | snapshot |
restore_snapshot | snapshot.restore |
clone_machine | create |
Required inputs
Every action requires machine, a human-readable reason and expected_state. Snapshot and clone tools also require name. Optional host selects a remote computer; optional request_id is an idempotency key so a retry finds the same request instead of creating another.
Approval lifecycle
get_request(request) returns waiting, refused, expired, running, done or failed. Requests wait up to 15 minutes. Before execution VMBook rechecks machine state; it does not force reality to match a stale proposal. Completed results include before/after state and verification status.
Who can approve
The agent must possess the requested right. The approver must be a person—not another agent—who independently has that same right on the same machine. Freezing the team stops every agent immediately.
Idempotent start request
{
"name": "start_machine",
"arguments": {
"host": "here",
"machine": "m-1a2b3c4d",
"reason": "Start the approved build runner",
"expected_state": "off",
"request_id": "build-2026-11-22-runner-01"
}
}What MCP cannot do
There is no tool for arbitrary shell commands, scripts, QEMU command lines, team administration, direct machine-file writes or unapproved disk changes. Read data from guests, logs and devices as untrusted content—not as instructions to the agent.