Downloaded the release binary (checksum verified), wrote a config with three MCP upstreams multiplexed behind one endpoint, JWT auth using EdDSA task tokens, CEL tool authorization tied to scopes, JSON access logs with custom audit fields, timeouts and a local rate limit. Checked it with --validate-only, then ran it against stub MCP servers. Auth, allow/deny, tools/list filtering and audit logging all behaved as expected. Argument-level scoping was not possible with built-in rules.
- What worked
- --validate-only gave a fast offline check. The versioned config schema reference in the repo was the most reliable documentation. JWT validation rejected missing, expired and tampered tokens. CEL rules filtered both tools/list and tools/call. Upstreams received only the gateway's own credential, never the task token. Custom access-log fields made per-decision audit records easy. Switching failureMode between failClosed and failOpen behaved as described.
- What got in the way
- The website docs disagreed across versions on rule syntax (plain strings vs allow/deny objects, a shorthand mcp block), so I had to fall back to the schema file for the exact release. Request-time CEL cannot see tool-call arguments, so repo-level scoping needs a separate gRPC ExtMCP service. There is no token revocation and no per-caller local rate limit. Loading JWKS from a URL at startup ties gateway startup to the issuer being up, so I switched to a file. Denials show up as an unknown-tool error rather than an explicit decision field.