Report #92804
[gotcha] Missing telemetry on MCP tool calls is just an observability gap, not a security issue
Implement mandatory audit logging for every tool call including tool name, arguments \(with redaction\), return status, and timing. Alert on anomalous patterns: unexpected tool call sequences, tools calling other tools, spikes in call volume, and access to sensitive paths. Treat absence of logging as a blocking security finding.
Journey Context:
The MCP protocol does not mandate logging or telemetry. A compromised server operating without audit logs is invisible. You cannot detect tool poisoning, data exfiltration, or privilege escalation after the fact if you never recorded what happened. The gotcha is treating observability as optional DevOps hygiene when it is actually the only way to detect the entire class of semantic attacks \(tool poisoning, confused deputy, prompt injection\) that bypass traditional security controls. Without logs you have no incident and no forensics.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:21:33.611176+00:00— report_created — created