Aegis Guardrails
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AEGIS_CLIENT | No | Identifies the coding agent host the MCP server was registered for; `aegis init` sets it at registration time (e.g. `codex mcp add aegis --env AEGIS_CLIENT=codex-cli -- ~/.local/bin/aegis-mcp` or `claude mcp add --scope user aegis -e AEGIS_CLIENT=claude-code -- ~/.local/bin/aegis-mcp`). | |
| AEGIS_MAX_JIT_TOKENS | No | Token budget for the rules returned by `aegis_scan` (default 2,000 tokens); equivalent to the `jit.max_tokens` config setting. | 2000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aegis_scanA | Call before editing files: returns the rules for |
| aegis_report_outcomeA | Call after verifying a change with tests or |
| aegis_create_ruleA | Builds a prompt for drafting a rule from |
| aegis_list_rulesA | Lists every rule with metadata and ledger fitness ( |
| aegis_capture_insightA | Appends a user correction or preference to |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role, and the descriptions explicitly resolve the two potential overlaps (aegis_scan vs aegis_list_rules, aegis_report_outcome vs aegis_capture_insight) by stating which one records state. The only residual confusion is that scan and list_rules both return rule sets, so an agent must read the fine print to pick correctly.
All names share the aegis_ prefix and follow a verb_noun pattern (create_rule, list_rules, report_outcome, capture_insight), with aegis_scan as the single verb-only deviation. Readable and predictable overall.
Five tools map cleanly onto the guardrails workflow: browse rules, generate a new rule, scan before editing, report verification outcome, and capture user corrections. Nothing appears redundant or padded at this size.
The rule lifecycle is incomplete: there is no tool to read, update, retire, or delete an existing rule (aegis_create_rule only builds a prompt and writes nothing), and captured insights cannot be reviewed or dismissed by the agent. These are notable gaps an agent would hit when maintaining rules, though core scan/report flows are covered.