-
Notifications
You must be signed in to change notification settings - Fork 1.9k
MCP access part 3: audit events and reporting #54779
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
0bf3eae
to
d7cee4b
Compare
@@ -4803,6 +4803,10 @@ message OneOf { | |||
events.AutoUpdateAgentRolloutTrigger AutoUpdateAgentRolloutTrigger = 213; | |||
events.AutoUpdateAgentRolloutForceDone AutoUpdateAgentRolloutForceDone = 214; | |||
events.AutoUpdateAgentRolloutRollback AutoUpdateAgentRolloutRollback = 215; | |||
events.MCPSessionStart MCPSessionStart = 216; | |||
events.MCPSessionEnd MCPSessionEnd = 217; | |||
events.MCPSessionRequest MCPSessionRequest = 218; |
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.
Does this work like app access where the requests get chunked up and stored in session recordings, or are we emitting every request directly to the audit log?
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.
they go straight to audit events similar to database queries. LLMs "execute" these requests based on user's behaves (like the inputs on the prompt) so don't expect a huge number of request to spam audit log. Any concern? we could introduce audit event vs recording mode for these but we never get to do that for database access.
…/54705_part_3_events
9acc0e1
to
7a02f9e
Compare
* MCP access part 3: audit events and reporting * add new icon, storybook, format
Related