RFC-003: Activity Log & Observability

[Dumbris]

Summary

This RFC proposes an Activity Log system for mcpproxy, providing complete visibility into what AI agents are doing.

Key Features

Feature	Description
Activity Recording	Tool calls, policy decisions, quarantine events
CLI Commands	mcpproxy activity list, watch, show, summary, export
REST API	/api/v1/activity with filtering, pagination, export
Web UI	Live-updating table via SSE, filters, detail panels
Intent Declaration	Optional agent-declared intent per tool call

Standards Alignment

• MCP SEP-1763: Interceptor framework compatibility
• OpenTelemetry GenAI: Semantic conventions for future integration
• Obot Pattern: MCPAuditLog reference implementation

Implementation Phases

Phase	Scope	Effort
Phase 1	Activity Log UX (DB, API, CLI, Web UI, SSE)	5-7 days
Phase 2	Intent Declaration (enhanced call_tool schema)	3-4 days

Storage Strategy

• BBolt DB: Hot storage for UI queries (30 days retention)
• JSON-lines logs: Text logs via lumberjack rotation (compliance/SIEM)

---

Question for Community

Should intent declaration be mandatory for call_tool?

Current proposal: Optional by default, configurable per-deployment.

Arguments for mandatory:

• Better security visibility
• Enables contradiction detection (RFC-004)
• Audit trail completeness

Arguments for optional:

• Backward compatibility with existing agents
• Reduced friction for simple use cases
• Gradual adoption path

---

Full RFC: https://github.com/smart-mcp-proxy/mcpproxy-go/blob/main/docs/proposals/003-activity-log.md

Related: RFC-004 (Security & Attack Detection) builds on this foundation.