Model calls have no output token limit
LowAV-RUNTIME-016Runtime safetyCore packNew in 2.0
What it finds
The agent calls the model with tools but never sets a maximum output size.
Why it matters
Without a cap, a looping or manipulated agent can generate very long outputs on every step — slow responses and a surprise bill.
What an attacker could do: Cost and latency per run are unbounded.
How to fix it
Set max_tokens / maxOutputTokens on every call, and a budget per run.
Pro shows the corrected code for your exact file, step by step, and re-scans to confirm the fix. See plans
Check details
- Finding code
- NO_OUTPUT_TOKEN_LIMIT
- How it detects
- Looks for a risky pattern, and stays quiet when a matching safeguard is present.
- Confidence
- Likely: strong signal, but review it in context.
- Scans
- Any text-based agent source or configuration (JS/TS/Python/JSON/YAML)
- OWASP LLM Top 10
- LLM04 - Model Denial of Service
- NIST AI RMF
- MG-2.2
- SOC 2
- A1.1
Check your agent for this
Paste your agent code or MCP config. The free scan runs all 124 checks in about 10 seconds — no account needed.
Related checks
- Command injection riskAV-RUNTIME-004 · Critical
- Unsafe dynamic code executionAV-RUNTIME-005 · Critical
- Privileged or host-mounted container configurationAV-RUNTIME-007 · Critical
- SQL query built from unescaped inputAV-RUNTIME-009 · Critical
- Unsafe deserialization of untrusted dataAV-RUNTIME-010 · Critical
- Prompt injection surface detectedAV-RUNTIME-002 · High