-
Notifications
You must be signed in to change notification settings - Fork 4
Adversarial Testing
Alessio Rocchi edited this page Jan 27, 2026
·
1 revision
Step-by-step guide for security-focused code testing.
- Security-critical code
- Authentication/authorization
- Payment processing
- API endpoints
- Data validation
{
"tool": "review_loop_start",
"arguments": {
"code": "function authenticateUser(...) { ... }",
"maxIterations": 3
}
}{
"tool": "review_loop_status",
"arguments": {
"loopId": "loop-id"
}
}{
"tool": "review_loop_issues",
"arguments": {
"loopId": "loop-id"
}
}{
"tool": "review_loop_get_code",
"arguments": {
"loopId": "loop-id"
}
}Input: Basic authentication function
Iteration 1: Adversarial finds SQL injection
Iteration 2: Coder fixes, Adversarial finds timing attack
Iteration 3: Coder fixes, Adversarial approves
Result: Hardened authentication function
Related:
Getting Started
Core Concepts
Agent Guides
- Overview
- Coder
- Researcher
- Tester
- Reviewer
- Adversarial
- Architect
- Coordinator
- Analyst
- DevOps
- Documentation
- Security Auditor
MCP Tools
- Overview
- Agent Tools
- Memory Tools
- Task Tools
- Session Tools
- System Tools
- GitHub Tools
- Review Loop Tools
- Identity Tools
Recipes
- Index
- Code Review
- Doc Sync
- Multi-Agent
- Adversarial Testing
- Full-Stack Feature
- Memory Patterns
- GitHub Integration
Advanced
- Plugin Development
- Custom Agent Types
- Workflow Engine
- Vector Search Setup
- Web Dashboard
- Programmatic API
- Resource Monitoring
Reference