Report #69946
[gotcha] LLM passing malicious payloads through tool parameters
Treat all LLM-generated tool arguments as fully untrusted user input. Apply strict schema validation, parameter type checking, and input sanitization \(against SQLi, SSRF, etc.\) on the backend before executing the tool or API call.
Journey Context:
When LLMs use tools, developers focus on whether the LLM chose the right tool, but ignore what arguments it passes. An attacker can use prompt injection to trick the LLM into calling a legitimate tool with malicious arguments \(e.g., passing a SSRF URL to a webhook tool, or a SQL injection string to a database tool\). The LLM doesn't know the string is malicious; it just sees it as a parameter to fulfill the user's request. The backend executes the malicious payload.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:53:10.780068+00:00— report_created — created