Skip to content

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

Merged
merged 3 commits into from
May 29, 2025

Conversation

greedy52
Copy link
Contributor

@greedy52 greedy52 commented May 13, 2025

@greedy52 greedy52 added no-changelog Indicates that a PR does not require a changelog entry MCP MCP Server related labels May 13, 2025
@greedy52 greedy52 force-pushed the STeve/54705_part_3_events branch from 0bf3eae to d7cee4b Compare May 13, 2025 21:44
@greedy52 greedy52 marked this pull request as ready for review May 13, 2025 21:45
@github-actions github-actions bot added audit-log Issues related to Teleports Audit Log size/md ui labels May 13, 2025
@github-actions github-actions bot requested review from kimlisa and kiosion May 13, 2025 21:45
@greedy52 greedy52 mentioned this pull request May 13, 2025
16 tasks
@@ -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;
Copy link
Collaborator

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?

Copy link
Contributor Author

@greedy52 greedy52 May 20, 2025

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.

@greedy52 greedy52 requested review from zmb3 and rudream May 23, 2025 15:27
@greedy52 greedy52 force-pushed the STeve/54705_part_3_events branch from 9acc0e1 to 7a02f9e Compare May 29, 2025 19:25
@greedy52 greedy52 enabled auto-merge May 29, 2025 20:01
@greedy52 greedy52 added this pull request to the merge queue May 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 29, 2025
@greedy52 greedy52 added this pull request to the merge queue May 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 29, 2025
@greedy52 greedy52 added this pull request to the merge queue May 29, 2025
Merged via the queue into master with commit 50e51be May 29, 2025
46 of 47 checks passed
@greedy52 greedy52 deleted the STeve/54705_part_3_events branch May 29, 2025 21:16
greedy52 added a commit that referenced this pull request Jun 26, 2025
* MCP access part 3: audit events and reporting

* add new icon, storybook, format
@greedy52 greedy52 mentioned this pull request Jun 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
audit-log Issues related to Teleports Audit Log MCP MCP Server related no-changelog Indicates that a PR does not require a changelog entry size/md ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants