You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added optional Peta Progressive Disclosure (PPD) for the MCP gateway. Deployments can now keep the existing flat tool list, expose a hybrid catalog-assisted flow, or switch to a strict catalog-first mode without changing the default behavior for existing clients.
Introduced gateway-native discovery tools: peta.catalog.search, peta.catalog.describe, and peta.catalog.execute, along with admin APIs for discovery config, profile management, preview, reindexing, and catalog stats.
Fixes and Improvements
Hardened discovery authorization and visibility handling so search, describe, and execute now stay aligned with normal server access, per-tool permissions, anonymous access rules, and approval-governed execution paths.
Fixed multiple hybrid-mode exposure issues, including direct tool filtering consistency, invalid profileId fallbacks, accurate tool counts, temporary server visibility, and runtime alias resolution for catalog execution.
Made catalog indexing safer and more resilient by avoiding destructive rebuild races, pruning stale rows correctly, skipping incomplete tool loads, and preventing temporary user-scoped server data from leaking into the global catalog.
Restored timeout reset behavior for uncached proxy requests and tightened discovery profile risk rule validation for more predictable runtime behavior.
Operational Notes
PPD remains default-off. If no enabled non-flat discovery profile is configured, the gateway continues to expose tools in the existing flat mode.
This release adds discovery-related Prisma schema changes and migrations, including new catalog/profile tables and cleanup of stale discovery visibility fields. Apply the bundled database migrations before enabling the feature in production.