Report #69647
[gotcha] Malicious documents trick the LLM into calling tools with unintended arguments
Implement strict authorization and confirmation flows for any state-changing or sensitive tool calls. Never grant tools more permissions than the user currently interacting possesses.
Journey Context:
Developers give tools broad permissions \(e.g., 'delete\_file' or 'send\_email'\) for convenience. If an indirect injection triggers the tool, the action executes with high privilege. The LLM cannot be the security boundary; the tool implementation must enforce RBAC and require user confirmation, treating the LLM as an untrusted orchestrator.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:23:05.085443+00:00— report_created — created