Adversarial red-team

Replay real attacks against your agent, not just clean traces.

Native plugins and Promptfoo privacy/security transpositions map to 46 observable attack classes, then combine with 10 delivery strategies across prompts, tools, RAG, MCP, memory and multi-agent execution — scripted or live.

Plugins say what; strategies say how

Select PII, prompt extraction, BOLA/BFLA/RBAC, SQL/shell/SSRF, MCP, memory poisoning or excessive agency, then deliver each probe directly, through guardrail-bypass framing, encoding, Unicode or multi-turn escalation.

  • 60+ native/compatible plugin IDs
  • 46 observable classes across F1–F6
  • 9 deterministic delivery strategies
  • A0 passive through A2 internal access

Scripted or live

Run attacks against a deterministic offline agent for repeatable regression tests, or against a real LLM endpoint to see how your actual agent responds under pressure.

  • Scripted mode: deterministic, no LLM cost
  • Live mode: your own model via BYOK
  • Pick a vertical, a count, or one specific class
  • Same detection pipeline as any other trace

A vulnerability report you can act on

Every probe is analyzed by the same AgentRisk pipeline, then organized into severity, defense rate, delivery method, risk category and a prioritized remediation report.

  • Critical-to-low vulnerability counts
  • Attack Success Rate and defense rate
  • Expandable families with one stored trace per probe
  • Prioritized fixes linked to the exact execution evidence

A five-minute campaign

Start with the deterministic scripted mode: select a vertical, A1, the agent_core preset and the balanced strategy profile, then run ten scenarios. Inspect the stored traces, fix the weakest channel, and repeat the same selection.

  • Healthcare, finance, legal, HR and customer support vaults
  • A0 benign, A1 external and A2 internal adversaries
  • Campaigns capped at 20 scenarios per request
  • Coverage tells you which plugins and strategies actually ran

Designed for safe regression testing

Use baseline on every pull request, balanced on protected branches, and complete or evasion on a scheduled security run. Live campaigns require an authorized OpenAI-compatible endpoint and BYOK; scripted campaigns stay offline and deterministic.

  • No platform LLM key required for scripted tests
  • Live mode replays the same scenario against the configured agent
  • Metrics: ASR, ELR, CLR and privacy score
  • Full reference: docs/redteam.md in the repository

Inside the capability

Three views of how it works.

ADVERSARIAL COVERAGE
CAMPAIGN 0712 TESTSINTOOLMEMOUTPROMPTENCODETOOLHANDOFFDEFENSE RATE75%

Attack every trust boundary

Measure prompt injection, tool misuse and exfiltration against every execution surface the production agent can reach.

DELIVERY STRATEGIES
PLUGINpii:directDIRECTbaselineENCODEbase64MULTI-TURNcrescendo

Vary how the probe arrives

Replay direct, encoded, jailbreak and multi-turn delivery without changing the vulnerability under test.

DEFENSE REPORT
DEFENSE REPORTv.07DEFENSE RATE75%prompt3tools7memory5handoff23 successful attacks2 remediations ready

Turn probes into engineering work

Rank successful attacks by severity, channel and remediation, then compare defense rate across campaigns.

The mental model

A clean benign trace does not tell you what an attacker would find.

Passive testing only shows what your agent does when nothing is trying to break it. AgentLeak preserves the published 32-class benchmark and extends it with 14 application-security classes, then varies the delivery strategy so a single direct refusal is not mistaken for complete protection.

Before

The only adversary your agent has faced is your own test suite.

With AgentLeak

A plugin × strategy matrix probes the exact boundaries the agent can cross.

  • The published 32-class taxonomy remains intact and 14 application-security classes extend it
  • Promptfoo-compatible plugins and delivery strategies remain separately measurable
  • Findings reuse the same channels, severity and AgentRisk score as any run

How it works

From raw trace to a fix, in four steps.

1

Choose vulnerabilities

Start with Privacy core, Agent security, Tool & MCP, or the complete 24-plugin suite; customize individual plugins when needed.

2

Choose delivery

Use the balanced profile or combine direct, jailbreak, markup, encoding, Unicode and four-turn Crescendo strategies.

3

The batch runs

Each generated scenario is executed and analyzed by the standard AgentLeak pipeline, exactly like a captured production trace.

4

Investigate and fix

Use the vulnerability report to rank weak attack surfaces, open the stored trace for any probe, then follow the remediation report and re-run the same batch.

Request body for a red-team batch

POST /api/projects/{project_id}/redteam
{
  "vertical": "healthcare",
  "n": 10,
  "adversary_level": "A2",
  "plugins": ["pii:direct", "mcp", "agentic:memory-poisoning"],
  "strategies": ["basic", "jailbreak-template", "crescendo"],
  "mode": "live"
}

Read the complete implementation guide →

FAQ

Questions, answered.

Ready when you are

Test the path, not only the answer.

Create a local workspace, run a bundled scenario, then wire AgentLeak into CI or let your agent onboard itself.