This release is a pre-release and may not be stable for production use.
AgentGuardian
Red-team your AI agents before attackers do.
Docs · Quickstart · Try the demo agent · Attack library · CI/CD · Sample report
AgentGuardian is an open-source red-teaming toolkit for AI agents. It scans your agent, maps the attack surface, runs the relevant adversarial agents, and generates evidence-backed findings for you to review — and fix the vulnerabilities before they reach production.
Quickstart
Requires Python 3.11–3.13.
1. Install
pip install agent-guardian
or
uv tool install agent-guardian
2. Add a model key
AgentGuardian drives its attacks with an LLM — Gemini, OpenAI, or Anthropic:
export GEMINI_API_KEY=... # or OPENAI_API_KEY / ANTHROPIC_API_KEY
See the configuration guide for all providers and options.
3. Check your setup
agent-guardian doctor
4. Run your first scan
No agent of your own yet? Point it at the hosted demo target — a deliberately vulnerable "finbot" banking agent:
agent-guardian scan \
--endpoint https://agent-guardian-testbench-u6tm6gzysq-uc.a.run.app/finbot/chat \
--model gemini:gemini-3.5-flash \
--mode fast
To scan your own agent, swap --endpoint for your target — local, staging, or production, any environment works as long as the endpoint is reachable.
5. Review the findings
AgentGuardian opens a live dashboard at http://127.0.0.1:7474 — watch findings land in real time, browse transcripts and evidence, and export reports.
Scan targets
HTTP agent
agent-guardian scan \
--endpoint http://localhost:8000/chat \
--model gemini:gemini-3.5-flash \
--mode smart
System prompt
agent-guardian scan \
--system-prompt ./prompts/customer-support-agent.txt \
--model gemini:gemini-3.5-flash \
--mode fast
In-process Python agent
agent-guardian scan my_app.agent:agent \
--model gemini:gemini-3.5-flash \
--mode smart
Point AgentGuardian at any importable Python callable or agent object (module:attr) and it runs in-process — useful for pre-deploy and CI, with nothing to host.
What AgentGuardian catches
AgentGuardian tests agentic risks that normal prompt scanners miss:
- Prompt injection and goal hijack
- Unsafe tool calls and tool chaining
- Privilege abuse
- RAG poisoning and indirect prompt injection
- Memory and context poisoning
- Sensitive data leakage
- Agent-to-agent manipulation
- Cascading failures
- Trust exploitation and unsafe outputs
- Goal drift and untraceable behavior
Every probe maps to OWASP Top 10 for Agentic Applications, MITRE ATLAS, and the CSA Agentic AI Red Teaming Guide — full per-ASI breakdown in the framework-coverage-matrix.
Reports & evidence
Every scan writes a signed, verifiable evidence bundle to ~/.agentguardian/scans/<scan-id>/:
| Artifact | What it is |
|---|---|
scan.json |
Machine-readable findings, signed (HMAC-SHA256 + Ed25519) |
events.jsonl |
The scan timeline |
probe/ |
Per-probe requests, responses, verdicts, and evidence |
forensic_manifest.json |
Integrity manifest for the bundle |
Export in any format, any time:
agent-guardian report SCAN_ID --output pdf --output-path report.pdf
Formats: json · sarif · junit · md · gitlab · pdf — see the sample report. Verify stored evidence with agent-guardian verify.
Scan modes
fast— quick local feedbacksmart— broader coverage for development and pull requestsfull— release gates and audit evidence
Use full when you need AIVSS-scored findings for CI/CD gates.
Commands
| Command | What it does |
|---|---|
agent-guardian scan |
Run an adversarial swarm scan against a target |
agent-guardian report <id> --output FMT |
Regenerate a report — json · sarif · junit · md · gitlab · pdf · badge |
agent-guardian gate <id> --fail-under N |
Apply pass/fail thresholds to a stored scan (CI exit codes) |
agent-guardian serve |
Start the local dashboard |
agent-guardian scans list / delete |
List or delete stored scans (delete --older-than 30d for bulk cleanup) |
agent-guardian config show / init |
Inspect the effective config / scaffold a config file |
agent-guardian verify <report> |
Verify the HMAC-SHA256 + Ed25519 signatures on a report |
agent-guardian last-score |
Print the AIVSS of the most recent scan |
agent-guardian doctor |
Verify the install, provider keys, and prerequisites |
agent-guardian version |
Print the installed version |
Run any command with --help, or see the CLI reference.
Run with Docker
docker build -t agent-guardian .
docker run --rm \
-e GEMINI_API_KEY \
-v "$HOME/.agentguardian:/root/.agentguardian" \
-p 7474:7474 \
agent-guardian scan \
--endpoint https://agent-guardian-testbench-u6tm6gzysq-uc.a.run.app/finbot/chat \
--model gemini:gemini-3.5-flash \
--mode fast
CI/CD with GitHub Actions
The shipped composite action runs a scan, uploads SARIF to GitHub Code Scanning, and (optionally) posts a summary comment on the pull request:
name: AgentGuardian
on:
pull_request:
push:
branches: [main]
jobs:
red-team:
runs-on: ubuntu-latest
permissions:
contents: read
security-events: write # upload SARIF to Code Scanning
pull-requests: write # post the summary comment
steps:
- uses: actions/checkout@v4
- uses: glacien-technologies/agent-guardian/.github/actions/agentguardian-scan@v1
with:
endpoint: http://localhost:8000/chat
model: gemini:gemini-3.5-flash
mode: full
fail-under: "80"
max-critical: "0"
comment: "true"
env:
GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
The job fails when the gate (fail-under / max-critical) is breached. For GitLab, Bitbucket, raw-CLI, and fleet/nightly setups, see the CI/CD guides.
Run from source
git clone https://github.com/glacien-technologies/agent-guardian.git
cd agent-guardian
python3.11 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
agent-guardian doctor
Contributing
We welcome new probes, new adapters, and new attacker logic. Start with the contribution guide and the good first issue label.
All commits must be DCO-signed:
git commit -s
By participating you agree to CODE_OF_CONDUCT.md and the ethics policy. AgentGuardian is for testing systems you own or are explicitly authorised to test.
Community
Join us on Discord for quickstart help, probe design, adapter questions, and roadmap discussion.
Security
To report a vulnerability, see SECURITY.md. Do not open public issues for security reports.
License
Apache-2.0. See LICENSE and NOTICE.
AgentGuardian is a trademark of Glacien Technologies. See TRADEMARKS.md for usage guidelines.
Metadata
Release files for agent-guardian 1.0.0rc41
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| agent_guardian-1.0.0rc41.tar.gz | 2.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_guardian-1.0.0rc41-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.1 MB
Release files / agent_guardian-1.0.0rc41.tar.gz
| Download URL | agent_guardian-1.0.0rc41.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2d40218b2e5de9359ff2e62243fa9acbd09d0169500ad6d5c28941a04dc4a88
|
|
BLAKE2b-256 checksum How to use checksums |
d99a3d20e0f449743e7836dc114833798718f1b10f9aab0553655316b3972d3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency logRelease files / agent_guardian-1.0.0rc41-py3-none-any.whl
| Download URL | agent_guardian-1.0.0rc41-py3-none-any.whl |
|---|---|
| Size | 1.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66049f593e36131189241a6e893c24b274bec0fd1a4c53f6921657d8440e337f
|
|
BLAKE2b-256 checksum How to use checksums |
a33728cbd3dc63ddf090e1440dccbf2964e42330536307442e5ad8057b3810c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency log