SignalNov 21, 20261 min read2 sources

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

In one minute

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:

Evidence / sources

  1. 1developers.googleblog.com/how-to-securely-connect-internal-cloud-run-mcp-servers-to-gemini-enterprise
  2. 2aws.amazon.com/blogs/machine-learning/connect-amazon-bedrock-agentcore-gateway-to-private-apis-in-a-hub-and-spoke-network-with-centralized-inspection
All Signals

Next reads

Read next

Open the graph
  1. 01topicGeminiExplore the gemini topic hub.
  2. 02topicGoogleExplore the google topic hub.
  3. 03topicMcpExplore the mcp topic hub.
  4. 04archiveSignalsOpen the signals and the raw-signal archive.
  5. 05sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract