feat(core) privacy annotations for tools, an experiment#1
Open
jstjoe wants to merge 2 commits into
Open
Conversation
- added types RequestPrivacy, ResponsePrivacy, DataCategory, Purpose, LegalJustification - added helper getRequestPrivacy(ctx) - unit tests - integration tests
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
1 participant
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.
This change introduces new optional non-breaking privacy hint annotation on tool definitions, tool requests, and tool responses.
Motivation and Context
Inform clients and servers of the potential privacy implications - universally without attachment to a specific governing framework - of making or serving a request as requested.
How Has This Been Tested?
Not yet. Just a simple sample server and client script. Will do.
Breaking Changes
Nope!
Types of changes
Checklist
Additional context
Inspired by SEP-1913