Skip to content
MoorAI
06 — defence & response

AI detection and response

Also written AI-DR

A security category for detecting, investigating and responding to threats in how AI is used — agents, model calls, MCP tools, AI applications — modelled on endpoint detection and response. An AI-DR control records what the AI did, alerts on risky behaviour and can block or contain it, rather than only reviewing models or configurations before deployment.

How MoorAI handles it: MoorAI checks what goes into an agent and what the agent reads, runs and replies, where it happens, and can coach, alert, mask, block, require a signed justification or end the session.

Related terms

  • On-device AI-DR Defence & response

    AI detection and response that runs on the machine where the agent runs, in or beside the agent process, rather than in a cloud service or network gateway…

  • Detection vs prevention Testing & measurement

    Detection notices something and produces a record; prevention stops it from happening. They are routinely conflated in agent-security claims, and the gap…

  • Runtime AIBOM Defence & response

    An AIBOM built from what is running and being used, not only from what is installed or declared: which model servers are listening, which MCP servers…

Defence & response

The vocabulary of running controls for agents: knowing what AI is present, cutting what it may do down to what it uses, catching misuse, and reconstructing an incident afterwards. Where MoorAI implements a term, a separate line under the definition says how; the definition itself stays vendor-neutral. To check one agent's configuration against these ideas, use the free permission right-sizer.

AI detection and response is term 1 of 10 in this part of the glossary.

Get started free Full glossary → How we test → Community agent on GitHub ↗

This page is one entry from the agentic AI security glossary, which defines 82 terms in the same style. Where a term belongs to a published taxonomy or standard — the HackAgent attack families, the OWASP lists, AMTSO's guidelines, MITRE ATLAS, ISO/IEC 42001, the NIST AI RMF, the EU AI Act, W3C Trace Context, the MCP specification — the authoritative wording is the source document's, not ours, and specifics should be verified there. "Lethal trifecta" is Simon Willison's term. OWASP® is a trademark of the OWASP Foundation; ATT&CK® and ATLAS™ are trademarks of The MITRE Corporation. Naming a framework here is description, not a claim of certification or endorsement.