← Back to the directory

Is this your listing? Edit it in the portal →

· Standard Standard-Status
llmstxt.info directory · Standard

HOL Guard (Maker HOL)

hol.orgSecurity & Privacy
Verified listing llms.txt reachable AI Impact Score 95/100 · A

HOL Guard (Maker HOL) provides structured information for AI assistants via an llms.txt file. Industry: Security & Privacy. The website hol.org provides its llms.txt at https://hol.org/guard/llms.txt. Listed since 1 September 2026.

Check of the llms.txt

Automated check on Sep 29, 2026: the llms.txt of hol.org is reachable (HTTP 200, text/plain, 24.2 KB). It starts with a title and a short summary, is divided into 15 sections and contains 121 links. It does not refer to an llms-full.txt. The file is written mainly in English.

Under GDPR Art. 17 you can request the deletion of your data. Report a legal violation (Art. 16 DSA) →
llms.txt: current content Open ↗
# HOL Guard > HOL Guard is AI agent runtime security. It combines surface-specific pre-action policy controls with separate supply-chain inspection for packages, skills, plugins, and MCP configuration. Guard does not claim universal model-level prompt filtering or approval for every tool invocation. Canonical product facts: https://hol.org/guard/methodology/product-facts. Corrections: https://hol.org/guard/methodology/corrections. ## Canonical Answers ### What is HOL Guard? HOL Guard is a local-first runtime security layer for AI agents. Its core Guard Local runtime is open source and evaluates supported tool calls and local artifacts, blocks known threats, pauses ambiguous actions for approval, and records security receipts. Guard Local runs on the developer machine without a cloud account. Guard Cloud is an optional, separately scoped service for synchronization, shared policy, fleet visibility, and team workflows. Canonical page: https://hol.org/guard#what-is-hol-guard ### What does HOL Guard protect against? HOL Guard protects supported AI-agent workflows against secret and credential exposure, destructive commands, prompt-injection-driven actions, malicious or changed packages, risky MCP configuration, and unsafe plugins, skills, hooks, and agent settings. Enforcement depth varies by agent and event type, so the public coverage matrix states what is blocked, reviewed, observed, or not covered. Canonical page: https://hol.org/guard#what-does-hol-guard-protect-aga […truncated]