docs(filesystem): clarify argless form behavior (Fixes #4423)#4426
Open
TomrroW007 wants to merge 1 commit into
Open
docs(filesystem): clarify argless form behavior (Fixes #4423)#4426TomrroW007 wants to merge 1 commit into
TomrroW007 wants to merge 1 commit into
Conversation
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.
Description
This pull request updates the
src/filesystem/README.mddocumentation to clarify server startup behavior and configuration auditing for directory access control.Documentation improvements:
(Note: Left the registry publishing note intact as per standard template instructions)
Server Details
README.md)Motivation and Context
Fixes #4423.
When the filesystem server is launched without path arguments, it correctly relies on the client's roots protocol for scope verification at runtime. However, this behavior makes the access boundary invisible at the config level. This PR adds a note to clarify this behavior and guides users who want an auditable, self-contained config to use explicit path arguments.
How Has This Been Tested?
N/A - This is purely a documentation update.
Breaking Changes
None. Users will not need to update their MCP client configurations.
Types of changes
Checklist
Additional context
N/A