The Intracept Registry
An open-source, structured database of CLI command translations. Human-written. Deterministic. No LLM involved.
Every entry maps a CLI tool and its flags to a plain-English translation, a verdict (allow / require_approval / deny), and a rationale explaining why.
How it works
The registry is a collection of TOML files, one per CLI tool. Each file defines the tool, its subcommands, and every flag with:
When an agent runs a command, Intracept parses it, looks up matching entries in the registry, composes the translation from individual flag translations, and enforces the strictest verdict.
Example entry
Each tool is a single TOML file in the registry. Here is git push with four of its flags:
Verdicts
Every flag in the registry is assigned exactly one verdict:
allowSafe command. Auto-approved, no user interaction required. The translation is shown inline for visibility but execution is never blocked.
require_approvalPotentially dangerous. The translation is shown to the user and they must explicitly approve before the command runs. Most destructive, network, or privilege-escalating commands fall here.
denyBlocked entirely. The command is never executed regardless of user input. Reserved for commands with no legitimate use in an agentic context (e.g., rm -rf /).
Tags
Tags categorize what a flag does. Organizations can write policy rules against tags (e.g., “deny all commands tagged data-exfiltration”).
destructiveDeletes or overwrites data irreversiblynetworkSends data to or fetches from external hostsprivilege-escalationElevates permissions (sudo, chmod, etc.)data-exfiltrationCould leak sensitive data to external systemsbypass-safetySkips hooks, checks, or verification stepsremoteModifies state on a remote server or serviceconfigurationChanges system or tool configurationfilesystemReads, writes, or modifies files on diskContributing
The registry is open source and contributions are welcome. To add a new tool or flag translation:
- Fork intracept-registry
- Create or edit the TOML file for the tool (e.g.,
registry/kubectl.toml) - Every flag entry must include:
translation,verdict, andrationale - Open a PR with a description of what the tool/flag does
Quality bar: Translations must be precise and unambiguous. They should explain what happens, not restate the flag name. “Force push” is not a translation; “Overwrite the remote branch history with your local history, permanently discarding any commits on the remote that are not in your local branch” is.
Browse the registry
View the full source, search entries, or contribute new translations.
github.com/laurenalexander2/intracept-registry