feat(config): add disabled_tools config option#91
Merged
Conversation
docs: fix read-only framing, remove stale list_commands, document disabled_tools
feat(server): skip registration of disabled tools
Resolve conflict in config/config.go: keep both DisabledTools field from this branch and AutoConnect field from main. Co-Authored-By: Claude Opus 4.6 <[email protected]>
…lguard into feat/disabled-tools-config
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DisabledTools []stringfield toconfig.Configfor disabling optional MCP toolsdisabled_tools: [provision, download_file]) and env var (SHELLGUARD_DISABLED_TOOLS=provision,download_file)provision,download_file,sleep— core tools (connect,execute,disconnect) cannot be disabledConfig layer only — server-side tool registration gating is in a separate PR.