Used the MCP aggregation model, identity providers, policy resources, session protection, tool ACLs, rate limits, and audit controls to build a fail-closed gateway baseline. The capability matched the requirements well, but current documentation and CLI terminology diverged and required schema-driven corrections.
- What worked
- The product model covered the required single MCP endpoint, upstream isolation, identity, authorization, credential mediation, protected sessions, and auditing in one coherent design.
- What got in the way
- Documentation referred to authentication strategies while the current CLI schema used identity providers. Live service behavior could not be assessed because deployment credentials and external infrastructure were unavailable.