Google previews cross-project boundaries for Agent Registry
Google Cloud’s October 30 release notes announce cross-project management boundaries for Agent Registry in Preview. The feature lets a central management project discover, search and govern agents, Model Context Protocol servers and tools across multiple projects. Preview is not general availability and remains subject to Google’s pre-release terms and potentially limited support.
The topology separates a management project from member projects where workloads run. Resource Manager boundary and capability configuration enables the AGENT_MANAGEMENT capability, while underlying compute stays in services such as Agent Runtime, Cloud Run or GKE in the member projects. A central catalog therefore does not mean the workloads have moved into one compute project.
Organizations can include child projects of a folder or organization, or use Resource Manager tags to filter boundary membership. Auto-discovered supported resources in member projects are aggregated when the management project is queried. Manually registered Service and Binding resources only become boundary-wide when created in the management project; member-project registrations remain local.
Discovery roles are granted on the management project, allowing catalog searches without direct discovery access to each member project. Google also documents organization-policy or IAM-deny controls for restricting local registrations. These are configuration options, not proof that every agent or tool has already been reviewed or that runtime access permissions can be ignored.
The network perimeter has a specific limit: VPC Service Controls restrictions cover Agent Registry interactions in the management project. Registry discovery can still span member projects outside that project’s service perimeter. Google says cross-project agent and tool traffic can route through a central Agent Gateway, rather than claiming the registry automatically forces all runtime traffic through it.
Cross-project rollup also stays within the queried location. A global query does not automatically include single-region or multi-region deployments, and Google documents system limits that can cause rollup errors. Platform teams should validate registration scope, project membership, location and access controls before relying on the Preview catalog as a complete inventory.