MCP server audit log blamed one service account for 40 change orders in three weeks

MityFourDoor · reddit · 2026-10-04

The team wired an internal MCP server into their product data system so staff could search parts, build assemblies from STEP files, and draft change orders from chat threads — cutting drafting from 10 minutes to 1.

The problem surfaced in the audit log: the connector authenticates as one service user, so every draft and edit is attributed to that account — 40 change orders in three weeks, all filed by "one person." Their quality lead asked how they'd answer that in an audit.

Fix: pass the requesting user as a field and treat the service account as transport only. But nothing enforces it — anyone calling tools directly bypasses attribution. The poster asks how others handle attribution on shared connectors. A real-world MCP enterprise governance case worth studying.

Original post →

More from coding & agent

coding & agent channel →