Topic starter
02/08/2026 9:41 am
TL;DR: OWASP’s LLM10: Unbounded Consumption describes how oversized prompts, expensive inference paths, and automated request floods can turn AI usage into a denial of wallet, with one 200k-token request costing $4 to $20 and 500 scripted requests draining tens of thousands of dollars in under an hour, according to StackHawk. The real control problem is not just abuse detection but enforcing resource limits before the model is asked to spend compute.
Editorial analysis by NHI Mgmt Group, based on content published by StackHawk: “Understanding and Protecting Against LLM10: Unbounded Consumption”.
Key questions
Q: What breaks when LLM applications do not enforce request limits before inference?
A: Without pre-inference limits, attackers can push large prompts, long contexts, or repeated calls into the model and force the organisation to pay for the abuse.
Q: Why do oversized LLM requests create both security and financial risk?
A: An oversized request consumes more tokens, memory, and compute than a normal API call, so the same access path can be used to degrade service and inflate cloud bills.
Q: How do teams know if LLM cost controls are actually working?
A: Look for stable cost per feature request, bounded cost per agent run, and no widening gap between median and p99 spend.
Practitioner guidance
- Implement pre-inference request gating Reject oversized prompts, excessive context windows, and expensive request patterns before they reach the model runtime.
- Set hard tenant and principal quotas Assign per-user, per-service-account, and per-tenant spend ceilings so no single identity can drain shared inference capacity.
- Add cost-aware anomaly detection Monitor token volume, latency spikes, burst rate, and unusual query shapes to detect denial-of-wallet behaviour early.
Bottom line: LLM unbounded consumption turns model access into a budget-exhaustion attack surface when request size and frequency are not bounded.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:35 pm
Unbounded consumption is a governance failure, not just an abuse pattern. The article shows that the control gap is not whether the model can answer a request, but whether the organisation can bound the cost of answering it. That makes consumption policy part of AI governance, spend management, and access control in the same control plane. Practitioners should treat budget exhaustion as a security outcome, not an accounting surprise.
A few things that frame the scale:
- The average time to mitigate a leaked secret is 36 hours, highlighting the operational burden of manual remediation processes, according to the 2024 State of Secrets Management Survey.
A question worth separating out:
Q: Should organisations treat LLM quota management as part of IAM?
A: Yes. If a user, service account, or agent can trigger expensive inference, then identity determines financial impact as well as access. Quotas, budgets, and throttles should be bound to identities and tenants, because the control question is not only who can call the model, but how much damage that caller can do.
👉 Read our full editorial: LLM unbounded consumption exposes a new cost-control attack surface