What problem does it solve? Security testers assessing RAG-backed applications lack structured guidance for attacking the vector storage and retrieval layer itself, as opposed to session-scoped prompt injection, and often report unverifiable findings like confabulated model outputs or same-session re-asks. ## Core Features & Use Cases - Persistent Corpus Poisoning Tests: Uploads poisoned documents and verifies the payload reaches a second, clean session via semantic retrieval on unrelated queries. - Cross-Tenant Vector-Store IDOR: Probes directly reachable vector databases (Chroma, Weaviate, Qdrant, Milvus, pgvector) and app-level namespace parameters for unauthenticated or unscoped corpus access. - Source-Text and Metadata Leakage Detection: Checks similarity-search and sources endpoints for raw chunk text belonging to other tenants, distinguishing it from true embedding inversion. - Use Case: While assessing a multi-tenant SaaS chatbot with document upload, you discover an exposed Qdrant port on :6333, list all collections without credentials, and prove unauthenticated full corpus read as a Critical finding. ## Quick Start Ask the agent to test the target application's RAG pipeline for vector-store weaknesses, starting with reachable vector-DB ports and cross-tenant retrieval checks.