Report #90479
[gotcha] Tool/Function Calling Injection via Compromised LLM
Apply strict input validation, parameterization, and least-privilege access controls to tool implementations, treating all LLM-generated arguments as entirely untrusted user input.
Journey Context:
Developers treat the LLM as the 'user' of the tool and assume it will send safe, well-formed parameters. However, if the LLM is compromised via indirect injection, it becomes an attacker proxy. It will attempt SQL injection in database tools or path traversal in file system tools. The tool backend must defend itself independently, exactly as it would against direct malicious user input.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:27:51.443280+00:00— report_created — created