---
id: "nr-agent-to-tool-traffic-is-being-pulled-inside-private-networks-with-cen-6eaf92"
slug: "agent-to-tool-traffic-is-being-pulled-inside-private-networks-with-cen-6eaf92"
type: "raw_signal"
title: "Agent-to-tool traffic is being pulled inside private networks with centralized inspection"
description: "Google Cloud published a five-step design for connecting Gemini Enterprise to internal MCP servers on Cloud Run without public exposure, using dual identity checks and scoped DNS."
observed_at: "2026-11-21"
record_date: "2026-11-21"
date_kind: "observed_at"
novelty: "notable"
source_platform: "newruntime.com"
topics: ["gemini","google","mcp"]
entities: ["Google Cloud","Gemini Enterprise","Cloud Run","Model Context Protocol","Egress Agent Gateway","Private Service Connect","Amazon Bedrock AgentCore","Amazon Bedrock AgentCore Gateway","Amazon VPC Lattice","AWS Transit Gateway"]
related_patterns: ["agent-protocols-become-interoperability-layer","agent-security-moves-to-runtime-boundaries"]
source_url: "https://developers.googleblog.com/how-to-securely-connect-internal-cloud-run-mcp-servers-to-gemini-enterprise"
source_urls: ["https://developers.googleblog.com/how-to-securely-connect-internal-cloud-run-mcp-servers-to-gemini-enterprise","https://aws.amazon.com/blogs/machine-learning/connect-amazon-bedrock-agentcore-gateway-to-private-apis-in-a-hub-and-spoke-network-with-centralized-inspection"]
why_it_matters: "Google Cloud published a five-step design for connecting Gemini Enterprise to internal MCP servers on Cloud Run without public exposure, using dual identity checks and scoped DNS. AWS describes a hub-and-spoke pattern that routes Bedrock AgentCore Gateway traffic to private APIs through a central firewall in both directions. Agent access to internal systems is now a network-architecture problem, not just a permissions setting."
verification_level: "source-linked"
signal_type: "synthesis"
synthesis_of: [{"slug":"how-to-securely-connect-internal-cloud-run-mcp-840ecc","title":"How to securely connect internal Cloud Run MCP servers to Gemini Enterprise","url":"https://newruntime.com/posts/how-to-securely-connect-internal-cloud-run-mcp-840ecc/"},{"slug":"connect-amazon-bedrock-agentcore-gateway-to-private-apis-3de588","title":"Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection","url":"https://newruntime.com/posts/connect-amazon-bedrock-agentcore-gateway-to-private-apis-3de588/"}]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "signal:agent-to-tool-traffic-is-being-pulled-inside-private-networks-with-cen-6eaf92"
retrieval_nugget: "Google Cloud published a five-step design for connecting Gemini Enterprise to internal MCP servers on Cloud Run without public exposure, using dual identity checks and scoped DNS."
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/signals/agent-to-tool-traffic-is-being-pulled-inside-private-networks-with-cen-6eaf92/","markdown":"https://newruntime.com/signals/agent-to-tool-traffic-is-being-pulled-inside-private-networks-with-cen-6eaf92.md","json":"https://newruntime.com/signals/agent-to-tool-traffic-is-being-pulled-inside-private-networks-with-cen-6eaf92.json"}
markdown_url: "https://newruntime.com/signals/agent-to-tool-traffic-is-being-pulled-inside-private-networks-with-cen-6eaf92.md"
---

# Agent-to-tool traffic is being pulled inside private networks with centralized inspection

## Retrieval answer

Google Cloud published a five-step design for connecting Gemini Enterprise to internal MCP servers on Cloud Run without public exposure, using dual identity checks and scoped DNS.

Google Cloud published a five-step design for connecting Gemini Enterprise to internal MCP servers on Cloud Run without public exposure, using dual identity checks and scoped DNS. AWS describes a hub-and-spoke pattern that routes Bedrock AgentCore Gateway traffic to private APIs through a central firewall in both directions. Agent access to internal systems is now a network-architecture problem, not just a permissions setting.

From the Field Notes:

- [How to securely connect internal Cloud Run MCP servers to Gemini Enterprise](https://newruntime.com/posts/how-to-securely-connect-internal-cloud-run-mcp-840ecc/) (2026-11-21)
- [Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection](https://newruntime.com/posts/connect-amazon-bedrock-agentcore-gateway-to-private-apis-3de588/) (2026-11-21)

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Gemini](https://newruntime.com/topics/gemini.md): Explore the gemini topic hub.
- topic hub: [Google](https://newruntime.com/topics/google.md): Explore the google topic hub.
- topic hub: [Mcp](https://newruntime.com/topics/mcp.md): Explore the mcp topic hub.
- collection: [Signals](https://newruntime.com/signals.json): Open the signals and the raw-signal archive.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)
