Aegis Gateway 2.0

Features: issue, solution, design, tests

Each entry has five parts:

COVERAGE-0.1-VS-2.0.md maps each 0.1 capability to its 2.0 replacement.


F1. Strict, bounded, dependency-free JSON

F2. Identity without credentials, and no token passthrough

F3. Credentials resolved only after governance

F4. Exposure, write unlock, per-tool groups, least-privilege listing

F5. Argument validation (schema subset)

F6. Resources by JSON pointer, never widened

F7. Resource scopes

F8. Policy: rules plus OPA, strict

F9. Egress: every destination, every DNS answer, any depth

F10. Rate limits and budget, atomic

F11. Circuit breaker

F12. Injection and poisoning screening

F13. Extension hooks over every governed operation

F13a. Hook modes and conditions

F13b. Out-of-process hooks (type: remote)

F13c. Read-only statement guard (type: sql-readonly)

F14. Per-call human approval

F15. Validate-run-promote receipts (DESTRUCTIVE)

F16. Tamper-evident audit, intent before execution

F17. Output bounding and redaction

F18. Tool catalog integrity (rug pull defence)

F19. Classification can only rise

F20. Dual-era MCP server (stateful 2025, stateless 2026-07-28)

F21. Hooking existing MCP servers (HTTP and stdio)

F22. Declarative REST tools (configuration only)

F22a. The 0.1 Java adapter modules become configuration

F22b. OpenTelemetry span export without an OpenTelemetry dependency

F23. Plugin sources and hooks via ServiceLoader

F24. Strict configuration

F25. The gateway’s own front door

F26. Knox 3.0 extension

F27. Multi Round-Trip Requests (2026-07-28)

F28. Governed resources, resource templates, prompts and completion

F29. Prompt definition pinning (rug pull for prompts)

F30. W3C trace context

F31. Decision metrics (Prometheus)

F32. Spark Connect source

F33. One-file Knox install

F34. Per-caller backend credentials (RFC 8693 token exchange)

F35. A2A agents as governed tools

F36. OpenAPI to a reviewable draft

F37. Reference hook services

F38. Container image and Helm chart

F39. Per-tool OAuth action scopes

F40. Signed server catalog and break-glass containment

F41. Offline policy test

Deviations from 0.1 conventions (for maintainer review)

  1. AGENTS.md rule: every MUTATE and DESTRUCTIVE tool must list approvalToken in required[]. 2.0 carries control values in _meta and advertises the 0.1 argument names as optional. If the token were required, a strict client could not make the first call that opens the approval request.
  2. Evaluation order: approval is evaluated after steps 5 to 8, as explained in F14. The step number (4) is unchanged.
  3. New deny codes: CATALOG_INTEGRITY and AUDIT_UNAVAILABLE (see DENY-CODES.md).