A shared agent can span organizational accounts without requiring every team to move its data into a platform-owned repository.
AWS states that a central platform account runs the agent using Amazon Bedrock AgentCore Gateway and MCP. AWS also states that line-of-business accounts keep their data in their own AWS accounts and expose it as MCP servers with secure cross-account access and fine-grained authorization. The mechanism is a federated tool boundary: the central agent invokes capabilities defined by each domain account, while authorization and the underlying data remain closer to the domain owner.
This matters as organizations move from single-team copilots to agents that need context across finance, operations, support, and product systems. The implication is that platform teams can standardize agent orchestration without automatically becoming the owner of every dataset. The evidence boundary is important: this is an AWS reference architecture and does not demonstrate production performance, operational cost, or the sufficiency of its controls in a specific enterprise. Watch whether deployments define tool-level permissions, identity propagation, audit logs, and revocation paths that remain intelligible across accounts.