06 — moorai terms

On-device

Detection and enforcement run in the process that is about to take the action, on the developer's machine, rather than in a cloud service the traffic is routed through. Two consequences follow. The decision is available in time to block rather than report. And calls that never generate network traffic — a local file read, a shell command, an in-process tool call — are governable, which no proxy or network gateway can do.

Related terms

PreToolUse hook Agents & architecture
A callback the agent host invokes after the model has requested a tool call but before the call executes, handing over the tool name and arguments and…
Action layer Agents & architecture
The enforcement surface at the tool call, as opposed to the prompt layer, which tries to classify text before the model sees it.

MoorAI terms

Product-specific vocabulary used across this site. The agent is open source (AGPL-3.0), so each of these is verifiable in the code rather than taken on trust.

On-device is term 2 of 5 in this part of the glossary.

Content-free detectionOn-deviceKeyed one-way hash Semantic escalation Normalization pre-pass

This page is one entry from the agentic AI security glossary, which defines 60 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 — 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.