Hermes Guardian
From its catalog listing
Deterministic allow/approve/block policies for Hermes tool calls, with read-only Policy Lab regression simulation and operator-reviewed policy proposals. Exact tool-name rules, explicit protected local paths, a deliberately limited shell grammar, and payload-free persistent decision audits. Unknown tools default to block; ambiguous recognized-tool arguments, invalid policy, and audit failures block. Uses the public pre_tool_call hook and native Hermes approval directives.
Good to know before installing
reads its own settings through Hermes and filesystem metadata and symlink targets for path comparisons; writes redacted JSONL under the active profile's plugin-data/hermes-guardian directory. No protected file-content reads, enforcement-hook network calls, subprocesses, model calls, credential storage, telemetry, core overrides, or self-updater. The operator CLI optionally uses public ctx.llm structured generation, sending instructions and policy paths to the configured provider, which may charge; no separate key is required. Explicitly confirmed activation uses ctx.set_config for atomic settings updates and stores private policy backups. Offline generation is a limited exact-language template. Approval rules follow host YOLO/approvals-off and unattended-mode settings; hard block rules do not ask for approval. A policy hook, not a sandbox: intended for a trusted local POSIX backend and trusted plugins that do not rewrite arguments after inspection.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-guardian - Said no? Turn it on later:
hermes plugins enable hermes-guardian - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Security & privacy
- Maintained by
- Oluseyix (Community)
- Needs
- No API keys declared
- Adds hooks
pre_tool_call- Works on
- linux, macos
- Needs Hermes
- 0.23.1 or newer
- Version
- 0.2.0
- In the catalog
- 2026-11-11
Known issues (from its catalog listing)
- No project-scoped positive permissions or Git push approval: unsupported Git commands block. Offline generation is template-based; live provider inference remains unverified.
- Simulation inspects current local path metadata; it does not prove final host authorization, audit availability or execution. Stop concurrent config editors during activation; storage failure can prevent rollback.
- Remote/container path namespaces, hard-link/case/mount aliases and filesystem races are not secured.
- Explicitly allowed tools outside the recognized file/terminal adapters receive tool-name checks only.
- Other plugins can rewrite arguments after the hook; disabled or failed-to-load Guardian provides no protection.
- The 16 MiB audit limit, write failure, partial trailing record or lock contention blocks calls until repaired or retried.
- Audit records describe policy decisions, not execution or final human approval.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in security & privacy
All security & privacy plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher