Report #21139
[gotcha] Malicious tool calling via indirect parameter injection
Enforce strict schema validation and authorization checks on the server side for \*every\* tool execution. Never trust the LLM to enforce security boundaries or assume it will only call tools with safe parameters.
Journey Context:
Developers assume the LLM will only call tools with safe parameters because the system prompt says so. But indirect injection can override this. If a tool has access to sensitive actions \(e.g., read\_file\), a malicious prompt in a retrieved document can trick the LLM into invoking it with attacker-controlled arguments \(e.g., read\_file\('/etc/passwd'\)\). The LLM is an orchestrator, not a security guard.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:53:39.120782+00:00— report_created — created