LLM10: Unbounded Consumption
Resource exhaustion via token bombs, expensive tool calls, or runaway agent loops driving cost or DoS.
Last reviewed July 2026
The gap LLM10 closes
In OWASP LLM Top 10, Unbounded Consumption addresses availability. Resource exhaustion via token bombs, expensive tool calls, or runaway agent loops driving cost or DoS. Penaxtra records this control at medium severity and establishes its state by exercising it against the running system, so the result reflects observed behavior rather than a documented assertion.
How Penaxtra delivers LLM10
Penaxtra ships adversarial probe families that target unbounded consumption directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by three independent judges and a meta-judge before it is recorded as a finding under the LLM10 identifier. The OWASP LLM Top 10 LLM10 identifier is attached when the finding is created, so it appears in the exported evidence pack already mapped to the control. Where the same weakness maps to another framework, the finding carries those control identifiers as well.
LLM10 capabilities
Findings tagged with the OWASP LLM Top 10 LLM10 identifier
Penaxtra severity for this control (medium)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
LLM10 compliance mapping
Findings for LLM10 carry the OWASP LLM Top 10 LLM10 identifier along with the corresponding control identifiers in the other frameworks Penaxtra maps, so one result is reflected across each mapped framework.
Frequently asked
What is LLM10 (Unbounded Consumption)?
Resource exhaustion via token bombs, expensive tool calls, or runaway agent loops driving cost or DoS. It is a OWASP LLM Top 10 control; Penaxtra assesses it at medium severity.
How does Penaxtra test for LLM10?
Penaxtra ships adversarial probe families that target unbounded consumption directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by three independent judges and a meta-judge before it is recorded as a finding under the LLM10 identifier.
Does a finding for LLM10 help with an audit?
Each finding is tagged with the OWASP LLM Top 10 LLM10 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.