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
Add --disable-write flag to control write operations (#385)
* Add --disable-write flag to control write operations
* Address PR feedback: Add alerting tools, tests, and documentation
- Add create_alert_rule, update_alert_rule, and delete_alert_rule to --disable-write flag
- Add comprehensive Read-Only Mode section to README documenting all disabled write tools
- Add tests to verify --disable-write flag behavior works correctly
* Add annotation write tools to --disable-write flag
- Include create_annotation, create_graphite_annotation, update_annotation, and patch_annotation
- Update README to document annotation tools in Read-Only Mode section
- Update tests to verify annotation write tools are properly disabled/enabled
@@ -250,6 +251,44 @@ The `mcp-grafana` binary supports various command-line flags for configuration:
250
251
-`--disable-pyroscope`: Disable pyroscope tools
251
252
-`--disable-navigation`: Disable navigation tools
252
253
254
+
### Read-Only Mode
255
+
256
+
The `--disable-write` flag provides a way to run the MCP server in read-only mode, preventing any write operations to your Grafana instance. This is useful for scenarios where you want to provide safe, read-only access such as:
257
+
258
+
- Using service accounts with limited read-only permissions
259
+
- Providing AI assistants with observability data without modification capabilities
260
+
- Running in production environments where write access should be restricted
261
+
- Testing and development scenarios where you want to prevent accidental modifications
262
+
263
+
When `--disable-write` is enabled, the following write operations are disabled:
0 commit comments