Repository navigation
Clarify direct-host network policy in MCP description - #236
Merged
Merged
Conversation
Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
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
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.
The shared
set_channel_networkdescription listed bridge/raw-socket exceptions but omitted/sudodirect-host execution. It now scopes enforcement to ordinary proxy-mode containers and explicitly states that direct-host policy is advisory, with no OS-level egress cutoff. Public/OFF connector rules, proxy private-address denial, and host credential/mount boundaries remain explicit.Adds a registered-schema regression and updates feature, test, and release notes. No handler or runtime enforcement changes.
Validation: regression failed before the description change; focused channel policy, network policy, and runtime access suites pass 23 tests with zero skips. Independent review and full candidate gates are coordinated separately before landing. Live dual-engine description acceptance remains separate.