What You’re Building
By the end of this guide (60 seconds), your AI will:- Detect prompt injection attacks in real-time
- Log threats without blocking (safe to deploy immediately)
- Work with LangChain, OpenAI, or any LLM pipeline
Installation
Initialize
~/.raxe/config.yaml with default settings.
Verify Installation
Your First Threat Detection
Now for the moment of truth. Run this command:Your AI would have been attacked. RAXE caught it.That prompt is a real injection attack used against production AI systems. Without protection, your AI would have leaked its system prompt, potentially exposing proprietary instructions, API keys, or business logic.
What Just Happened
In under 5 milliseconds, RAXE:- L1 Rules - Matched the input against 515+ detection patterns covering prompt injection, jailbreaks, data exfiltration, and more
- Threat Classification - Identified this as a prompt injection attack (pi-001) with HIGH severity
- Action - Logged the detection (default: log-only mode means your app keeps working)
Log-only mode is intentional. RAXE defaults to logging threats without blocking so you can safely deploy to production, observe real attack patterns, and then enable blocking once you trust the detections. No false positives crashing your users.
Protect Your First Agent
LangChain Agent (2 lines)
agent.py
CrewAI Multi-Agent Crew
crew.py
AutoGen Conversational Agent
autogen_agent.py
MCP Server Protection (Claude Desktop/Cursor)
Protect any MCP server with a single command:~/.config/claude/claude_desktop_config.json):
Direct Scanning
CLI
Python SDK
app.py
OpenAI Wrapper
app.py
What RAXE Scans
| Scan Point | Description | Status |
|---|---|---|
| PROMPT | User input to agents | Available |
| RESPONSE | LLM outputs | Available |
| TOOL_CALL | Tool invocation requests | Available |
| TOOL_RESULT | Tool execution results | Available |
| AGENT_ACTION | Agent reasoning steps | Available |
| RAG_CONTEXT | Retrieved documents | Available |
| SYSTEM_PROMPT | System instructions | Coming soon |
| MEMORY_CONTENT | Persisted memory | Coming soon |
Going to Production
You now have threat detection running. Here’s the path to full protection:Monitor (Week 1)
Run in log-only mode. Review detections in your logs to understand your threat landscape.
Tune (Week 2)
Adjust sensitivity if needed. Add custom rules for your domain. See Custom Rules.
Production Checklist
-
raxe doctorpasses - Integration added to all agent entry points
- Log aggregation configured to capture RAXE logs
- Alerting set up for CRITICAL severity detections
- Team reviewed 1 week of detection logs
CE includes 1,000 scans/day. For higher volumes, see pricing.
What’s Next?
MCP Gateway
Protect Claude Desktop & Cursor
LangChain Guide
Full LangChain integration
CrewAI Guide
Multi-agent crew protection
Detection Rules
Explore 515+ detection rules
