What is an AI agent?
Start here if the tool-calling loop is new to you. Every attack in this track works through that loop.
Learn · Track
How agents get attacked through the text they read and the tools they call, and the layered controls that limit the damage, including how to keep personal data and secrets out of prompts, logs and traces. You should know what an agent and a tool call are; the agents track covers both.
Direct and indirect prompt injection explained with agent examples, why filters alone fail, and the layered defenses OWASP and recent research recommend.
The ten OWASP LLM risks for 2025, one by one, with what each looks like in an agent that calls tools and a concrete control for each one.
Why an agent with private data, untrusted content and a way to send data out is one prompt injection from a leak, and how to break the combination.
The main MCP security risks from the spec and OWASP: tool poisoning, rug pulls, shadowing, confused deputy, token passthrough, SSRF and their controls.
Why AI agents drift to more access than they need, the layers to narrow (servers, tools, arguments, data, people, keys) and how to keep them narrow.
Where personal data and secrets leak in an AI app (prompts, tool arguments, logs, answers) and how masking, tokens and a controlled reveal contain them.
Start here if the tool-calling loop is new to you. Every attack in this track works through that loop.
Next: catch regressions, including security ones, before a change reaches production.
This website (not the L2M product) uses Google Analytics, only after you accept cookies. Cookie settings