You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(cli): add --read-only flag to disable write operations (#41)
* feat: add --read-only flag to disable write operations
Add a new `--read-only` CLI flag that disables tools which perform
write operations (delete, patch, scale, create, apply, etc.).
This enables deploying the MCP server in read-only mode for:
- Observability-only use cases (monitoring, troubleshooting)
- Environments with read-only service accounts
- Compliance requirements separating read/write capabilities
Tools are categorized as read-only or write operations:
- K8s: 8 read-only, 14 write tools
- Helm: 3 read-only, 3 write tools
- Istio: 9 read-only, 3 write tools
- Cilium: ~25 read-only, ~15 write tools
- Argo: 4 read-only, 4 write tools
- Prometheus/Kubescape/Utils: all read-only (unchanged)
Co-Authored-By: Claude Opus 4.5
Signed-off-by: Matteo Mori <matteo.mori@rvu.co.uk>
* fix: disable shell tool in read-only mode
The utils provider exposes a `shell` tool that executes arbitrary
commands, bypassing read-only restrictions. In read-only mode, this
tool is now disabled.
Also pass readOnly to all providers (kubescape, prometheus, utils)
for consistency with the existing providers.
Signed-off-by: Matteo Mori <matteo.mori@rvu.co.uk>
---------
Signed-off-by: Matteo Mori <matteo.mori@rvu.co.uk>
0 commit comments