feat: add client-side tool guard - #5
Merged
Merged
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.
Summary by cubic
Adds a configurable client-side guard that evaluates every
call_toolinvocation before tool lookup, discovery, or transport dispatch, so non-allowed calls never reach a native transport.allow,deny,review, anderrorverdicts; onlyallowdispatches, exactly once.reviewverdict requires anapprove(call, review_verdict)method that must returnallow, otherwise the call fails without dispatching.bypass_toolsallowlist skips guard evaluation for intentionally safe, client-owned tools.guard_*errors including the tool name, args, and verdict.evaluate(call); existing clients without aguardconfig are unaffected.Docs and examples
utcp.guard.Written for commit 8931398. Summary will update on new commits.