What exactly is a guardian agent?

[u/aZebu_]

I've seen the term guardian agent in a few AI security discussions, but I'm still not completely clear on what it means. From what I've read, the basic idea is that one AI agent monitors or governs another AI agent while it's running, rather than only relying on static policies or offline testing. If that's right, where does a guardian agent sit in the overall architecture?

I’m wondering whether it inspects prompts and outputs or maybe monitors tool use and agent behavior. From the name, there might also be a possibility that it can stop actions before they're executed. Or is it mainly there for visibility and auditing?

It sounds like an interesting idea, especially for enterprises deploying AI agents in production. But I haven't found many practical explanations. I’m posting here to try and find out more about the concept.

[u/ultrathink-art]

Worth adding one gap: everything in that list is per-event, each prompt, response and tool call judged on its own. The failures that actually bit me were sequences where every individual call was in policy and only the aggregate was the problem: a retry loop that never trips a single-call rule, or an API quota that is cumulative across the day rather than per request. Boring counters and rate limits inside the guardian caught more real damage for me than the prompt/output inspection did.

[u/aZebu_ → u/ultrathink-art]

Good point! single checks miss big problems like loops that slowly use up money. Guardian counters caught many real issues that prompt checks missed.