-
Notifications
You must be signed in to change notification settings - Fork 115
fix: allow connect tool on readOnly mode #499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes an issue where the connect tool was inadvertently removed from read-only mode operations when it was moved from the "metadata" category. The change ensures that connection operations remain available in read-only mode since they don't modify data.
- Added "connect" to the list of allowed operation types in read-only mode
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Pull Request Test Coverage Report for Build 17382802347Details
💛 - Coveralls |
* main: feat: add more details about atlas connect flow - MCP-124 (#500) chore: extend library interfaces to allow injecting a custom connection error handler MCP-132 (#502) fix: start mcp even if connection fails - [MCP-140] (#503) fix: allow connect tool on readOnly mode (#499) chore: warn about the usage of deprecated cli arguments MCP-107 (#493) ci: add ipAccessList after creating project (#496)
Proposed changes
metadatacategory, after we updated it, it got removed from thereadOnlytools. This is needed to be able to use read operations.Checklist