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
rootCmd.PersistentFlags().Bool("strict-toolsets", false, "Fail startup if configured toolsets include unknown names")
141
143
rootCmd.PersistentFlags().Bool("read-only", false, "Restrict the server to read-only operations")
142
144
rootCmd.PersistentFlags().String("log-file", "", "Path to log file")
143
145
rootCmd.PersistentFlags().Bool("enable-command-logging", false, "When enabled, the server will log all command requests and responses to the log file")
Copy file name to clipboardExpand all lines: docs/server-configuration.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -336,6 +336,40 @@ Starts with only discovery tools (`enable_toolset`, `list_available_toolsets`, `
336
336
337
337
When both dynamic mode and specific tools are enabled in the server configuration, the server will start with the 3 dynamic tools + the specified tools.
338
338
339
+
### Strict Toolset Validation
340
+
341
+
**Best for:** Locked-down environments where toolset allow-lists must fail closed.
342
+
343
+
By default, unknown toolset names are ignored and logged as warnings so existing configurations remain backward compatible. If you want startup to fail when a configured toolset name is unknown, enable strict validation.
Use this when a typo in a toolset name should be treated as a startup error instead of silently falling back to a narrower or unintended capability set.
0 commit comments