Feature flag rollout: mcp_session_audit_events

Summary

Roll out the feature currently behind the mcp_session_audit_events feature flag.

Introduced by !260242 (merged) (milestone 19.6, type: wip, default_enabled: false). Definition: ee/config/feature_flags/wip/mcp_session_audit_events.yml.

Note

Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle

What could go wrong?

  • Audit event volume: one ai_tool_invoked event per MCP tool call, plus a second event on failure. Watch audit event write throughput and storage before raising the percentage.
  • Latency: audit scope resolution is permission checked per call, unlike telemetry scope. A slow or repeated authorization check shows up directly in MCP tool call latency.
  • Wrong scope: scope comes from the argument each tool declares as its container (id for get_pipeline, project_id for get_project). A tool declaring the wrong argument routes records to the wrong customer's SIEM stream. Verify a sample of emitted events per tool family.
  • Silent gaps: auditing is designed never to raise, so failures are invisible in the tool response. Check exception logs rather than relying on user reports.
  • Second gate: storage is still gated by ai_audit_events_storage_enabled, so events can be emitted without being persisted.

Events

Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging

Rollout

Run all production chatops commands in #production and cross-post the results to #<slack-channel-of-dri-team>. Background: incremental rollout process, feature actors.

Non-production

  • 50% of actors: /chatops gitlab run feature set mcp_session_audit_events 50 --actors --dev --pre --staging --staging-ref
  • Fully on: /chatops gitlab run feature set mcp_session_audit_events true --dev --pre --staging --staging-ref

Production — percentage rollout, waiting at least 15 minutes between steps and watching the dashboards above:

  • /chatops gitlab run feature set mcp_session_audit_events <percentage> --actors

Or target specific actors instead:

  • By project: /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss mcp_session_audit_events true
  • By group: /chatops gitlab run feature set --group=gitlab-org,gitlab-com mcp_session_audit_events true
  • By user: /chatops gitlab run feature set --user=harsimarsandhu mcp_session_audit_events true

Before global rollout

Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:

Cleanup

Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and ee/config/feature_flags/wip/mcp_session_audit_events.yml from the codebase, then:

  • /chatops gitlab run release check <merge-request-url> <milestone>
  • /chatops gitlab run feature delete mcp_session_audit_events --dev --pre --staging --staging-ref --production

Rollback

  • Production off: /chatops gitlab run feature set mcp_session_audit_events false
  • Non-production off: /chatops gitlab run feature set mcp_session_audit_events false --dev --pre --staging --staging-ref
  • Remove entirely: /chatops gitlab run feature delete mcp_session_audit_events --dev --pre --staging --staging-ref --production
Edited by 🤖 GitLab Bot 🤖