feat: --read-only flag to disable write tools#28
Conversation
Introduces a new `--read-only` command-line flag. When set to true, this flag disables all tools that can modify bug states, ensuring the server operates in a read-only capacity.
|
@lemenkov JFYI This feature filters the methods which modify a bug via tool tags property. In case, you want to add more tools which alter bugs, please keep that in mind. Also, this feature overlaps with the currently, my thought is:
This way it is simpler and easier for user & us to maintain. don't let the user mix both options |
|
Surprisingly, having both options does not have any side effects in the program. Maybe we can allow it side by side. Let me test it further, |
|
Both methods looks good (env-var and cli switch). Although MCP_BUGZILLA_DISABLED_METHODS looks more fine-grained I really don't see a reason to selectively disable any RO-methods. From my understanding disabling RW-methods makes much more sense in some configurations while selecting RO-metholds doesn't add up. But anyway I'm fine with both approaches. |
|
The |
The `cli_args` are now stored directly as an argparse.Namespace object, simplifying access to individual arguments and improving type hinting. The README has been updated to reflect this change and clarify the interaction between the `--read-only` flag and `MCP_BUGZILLA_DISABLED_METHODS`.
2 participants
Introduces a new
--read-onlycommand-line flag. When set to this flag, disables all tools that can modify bug states, ensuring the server operates in a read-only capacity.