06 — moorai terms

Content-free detection

design constraint

Analysis that happens on the device, where only the verdict leaves it — a category, a risk level, a decision and a keyed one-way hash — never the prompt, the file, the arguments or the path. The point is that a security control which centralises prompts becomes the largest concentration of sensitive text in the company. Content-free means the console can prove what happened without ever holding what was said. The one exception is an opt-in capture tier an administrator has to turn on explicitly.

Related terms

  • On-device MoorAI terms

    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…

  • Keyed one-way hash MoorAI terms

    A tenant-keyed cryptographic digest of a value — a tool argument, a file path, a detected secret — emitted in place of the value itself.

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.

Content-free detection is term 1 of 5 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 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.

glick.run — AGPL-3.0