Report #7384
[gotcha] Executing MCP tools without logging the full argument payload and decision context
Implement structured logging for all tool calls, including the LLM's reasoning/thought process that led to the call, and the exact arguments passed.
Journey Context:
When an agent goes rogue or is compromised, developers often have no idea why it took an action. Standard logging only shows 'tool X called'. Without logging the LLM's preceding thought process or the exact arguments, post-incident forensics are impossible. You cannot reconstruct the prompt injection payload that triggered the malicious action. The tradeoff is increased storage cost and potential PII in logs, but it is essential for security observability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T02:38:00.058771+00:00— report_created — created