8 articles tagged offensive-security
The word agent gets used for a chatbot with a system prompt, a script in a loop, and a system that plans and acts on its own. Three different animals. Only one can hurt you. A red teamer's guide to what an AI agent actually is and what agentic really means.
The autonomy that lets an agent clear your overnight queue is the same autonomy that lets one poisoned document turn it against you. One property, two sides. Why the more agentic the system, the further a single injection travels.
You will never make the model deterministic. So stop trying. You make the system around it deterministic, shrink the part that needs judgment to almost nothing, and put a fence around what's left. Here is how that actually works.
Prompt injection, jailbreaks, exfiltration, poisoning, tool abuse, excessive agency. The map of how every AI system breaks, whether you are attacking one or defending your own agent. A red teamer's working taxonomy.
Agentic AI for Offensive Security, Part 9. CLIs and MCP turn an agent's decisions into actions. A useful tool interface also tells you what was authorized, what reached the target, what failed and what the resulting evidence can support.
Every team is wiring agents to MCP servers with the same casual trust they once showed Dropbox installs. The attackers have already noticed.
Claude Code is the best AI tool I've found for offensive security, but these concepts work with Gemini and other powerful AI agents too. Here's how to build your first AI red team skill and why it changes everything about how you operate.
A manual recon of an AI application takes 2-4 hours. With Claude Code and kali-mcp, it takes 12 minutes. Here's the exact workflow with working skills you can copy.