No execution rate limiting
LowAV-RUNTIME-003Runtime safetyCore pack
What it finds
Absence of `rate limit`, `throttle`, `budget`, `max calls`, or `quota` patterns.
Why it matters
Agents without execution budgets can exhaust API quotas and create denial-of-service conditions.
How to fix it
Add rate limits, token budgets, and maximum call counts to all execution paths.
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_RATE_LIMITING
- How it detects
- Flags a safety control that should be there but is not.
- Confidence
- Likely: strong signal, but review it in context.
- Scans
- Agent source with detectable execution behavior
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