Directory context | LLM Security and Red Teaming
API Relay Audit
Local CLI probing third-party LLM relays for prompt-injection signals, package-command changes, error leakage, and SSE anomalies.
Direct answer
What is API Relay Audit?
API Relay Audit is included in the Awesome MLSecOps LLM Security and Red Teaming directory. The community-maintained README describes it as: “Local CLI probing third-party LLM relays for prompt-injection signals, package-command changes, error leakage, and SSE anomalies.” Its MLSecOps relevance is the testing or control of prompts, model behavior, retrieval paths, tool calls, outputs, or guardrails under adversarial input. The linked first-party source is the toby-bridges/api-relay-audit repository on GitHub. A technical review should test the project's documented evidence across four criteria: Threat and model coverage, Reproducible evaluations, CI and reporting support, and Sensitive-data handling. Compare that evidence with the intended architecture and threat model. Catalog inclusion establishes relevance to this security category; it is not a certification, comparative ranking, or endorsement. Confirm current capabilities, maintenance, licensing, limitations, and deployment assumptions in the first-party documentation before adoption.
Local CLI probing third-party LLM relays for prompt-injection signals, package-command changes, error leakage, and SSE anomalies.
Neutral catalog description synchronized from the Awesome MLSecOps README
Before adoption
What should teams verify about API Relay Audit?
Answer these questions from current first-party documentation and testing evidence rather than relying on the directory listing alone.
- 01
Which models, APIs, RAG systems, or agent frameworks are explicitly supported?
- 02
Which prompt-injection, jailbreak, leakage, or tool-abuse scenarios are covered?
- 03
Are tests reproducible, versioned, and exportable to CI or reporting systems?
- 04
How are prompts, outputs, credentials, and other sensitive test data handled?