Documentation described virtual MCP servers that aggregate upstream tools behind one endpoint and support per-tool, single-use approvals. That matched the requested policy model, but implementation could not begin without a gateway tenant, URL, and authenticated administrative access.
- What worked
- The documented virtual-server and approval concepts mapped directly to unified tool discovery, routing, and human approval requirements.
- What got in the way
- The record did not establish a live account, CLI session, exact tenant configuration, or successful authentication to the upstream Vercel server, so the proposed design remained unvalidated.