Repository navigation
v0.6.0
v0.6.0 — Server-level read-only mode
This release adds a read-only mode that reduces the server's tool surface at
registration time (#31).
It is defense in depth next to the MCP gateway's allow/ask/deny policy and keeps
tools/list small for read-only clients.
Read-only mode
Start the server with --read-only, or set
MCP_SERVER_DOCKER_READ_ONLY=1 (1/true/yes/on, case-insensitive):
"args": [
"--from",
"git+https://github.com/dboeckli/mcp-server-docker@v0.6.0",
"mcp-server-docker",
"--read-only"
]"env": {
"MCP_SERVER_DOCKER_READ_ONLY": "1"
}For the sbx MCP gateway, append --read-only to the comma-separated --args
list, e.g. sbx mcp add docker --args "--from,...,mcp-server-docker,--read-only".
Behavior
- Default mode is unchanged: all 31 tools.
- Read-only mode exposes the 17 tools annotated with
readOnlyHint=true. - The 14 write/destructive tools are not registered: they are absent from
tools/listand calls to them returnUnknown tool. - The container
logs/statsresources and thedocker_composeprompt remain
available; both resources are read-only and the prompt executes nothing. - The filter is one central
is_tool_enabledpredicate, so
disable-destructiveand enable/disable lists can be added later without
touching individual tools.
Read-only mode is a best-effort guardrail, not a sandbox boundary. The process
still has host Docker access; keep gateway policy and sandbox isolation in
place.
Compatibility
No breaking changes. Default tool names, schemas, resources, and prompts are
unchanged.
Changes
- #39 — add server-level read-only mode (
--read-only/MCP_SERVER_DOCKER_READ_ONLY) - #40 — bump version to 0.6.0
Full Changelog: v0.5.0...v0.6.0