v1.3.0

With homebutler mcp --max-risk read, an agent can look at your servers and change nothing through this process.

Two boundaries come with that sentence. Read mode stops changes, not reading: docker_logs and docker_inspect show whatever a container printed or was configured with, and network_scan pings the whole subnet. It also covers this MCP process only, so the CLI and homebutler serve on the same machine are unaffected. report stays available in read mode and never saves a snapshot there, so an agent can still be asked what changed. Without the flag, the server offers every tool, as before.

✨ Features

• homebutler mcp --max-risk read|write|destructive sets the highest tool class the MCP server offers (#348). With read, an agent can look but this server changes nothing: tools above the ceiling are left out of tools/list and refused when called by name, with an error naming the ceiling, and report always runs as no_save against the last snapshot saved by cron or by hand. The default is destructive, every tool, as before. Read mode stops changes, not reading, and docs/mcp-server.md says which read tools ask things outside the machine (network_scan pings the subnet). A reduced tools/list is marked cacheScope: private so a shared cache cannot hand it to another client