Unbounded memory persistence
LowAV-RUNTIME-001Runtime safetyCore pack
What it finds
A `persist: true`/`ttl: null`/`retention: forever` pattern.
Why it matters
Agents that retain data beyond session boundaries can act on stale or poisoned context.
How to fix it
Set an explicit TTL on all memory; clear session context after task completion.
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
- UNBOUNDED_MEMORY
- How it detects
- Looks for a specific risky pattern in the code or config.
- Confidence
- Definite: the risky setting is written plainly in the file.
- Scans
- Agent memory/session configuration
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