Why (roadmap: Next)
Per docs/GOVERNED-MCP.md (deferred item): MCP tool calls are audited against the live per-run sink, but the pre-run discovery connection (initialize / tools/list in registerMcpServers, src/agent/session.ts) runs before the run's AuditSink exists — its egress is enforced but not recorded in the run chain.
Sketch
Options (design discussion welcome):
- Buffer discovery
mcp_request events and append them right after run_start.
- Record a per-session discovery record in the session journal with connection summaries + anchor.
Acceptance
A reviewer reading one run's chain can see which MCP servers were contacted during discovery, with host + outcome, under the same minimization rules (no headers/args/bodies).
Why (roadmap: Next)
Per docs/GOVERNED-MCP.md (deferred item): MCP tool calls are audited against the live per-run sink, but the pre-run discovery connection (initialize / tools/list in
registerMcpServers,src/agent/session.ts) runs before the run's AuditSink exists — its egress is enforced but not recorded in the run chain.Sketch
Options (design discussion welcome):
mcp_requestevents and append them right afterrun_start.Acceptance
A reviewer reading one run's chain can see which MCP servers were contacted during discovery, with host + outcome, under the same minimization rules (no headers/args/bodies).