Report #93969
[gotcha] Attackers crafting inputs that cause the LLM to enter infinite tool-use loops, draining API credits or causing DoS
Implement strict rate limiting, token limit caps per request, and hard limits on the maximum number of tool calls per conversation. Avoid recursive prompt patterns where the LLM's output is fed back as input without bounds.
Journey Context:
An attacker might exploit a tool-use loop where the LLM keeps calling a tool with the output of the previous call \(e.g., a 'search' tool that returns a prompt to search again\). This consumes massive compute and API costs. Developers often forget to cap the maximum number of agentic loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:18:47.763194+00:00— report_created — created