fix: Add conditional check for ProfileTool usage based on repository …#717
Merged
binaryk merged 1 commit intoBinarCode:10.xfrom Feb 13, 2026
Merged
Conversation
|
@LAlex14 is attempting to deploy a commit to the BinarCode Team on Vercel. A member of the Team first needs to authorize it. |
PR Summary
|
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
2 participants
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.
Fix ProfileTool boot condition to respect
canUseForProfilemethodProblem
ProfileToolwas being registered in MCP tools regardless of whether repositories defined acanUseForProfile()method that returnedfalse. This was inconsistent withProfileController, which already respects this method to control access.Solution
Added the same
canUseForProfilecheck used inProfileController(line 39) toBootMcpTools(line 156-157). NowProfileToolis only registered if:canUseForProfilemethod doesn't exist (default allow), ORtrueThis ensures consistent behavior between the controller and MCP tool registration.