AWS’s AtScale walkthrough grounds that claim in a specific architecture. Observed fact 1: one deployed dimensional model is exposed over SQL, XMLA, and MCP, so the agent and existing BI tools use common definitions. Observed fact 2: the example places joins, metric definitions, and row and column filters in the semantic layer rather than in the prompt. Observed fact 3: AWS describes propagating human identity through Bedrock AgentCore Identity to AtScale, where RBAC and row security are applied at query time.
Mechanism: The semantic model mediates between agent query planning and governed data access: Strands uses MCP while AtScale applies declared metrics, joins, and caller-specific controls; AgentCore hosts the agent and manages its outbound credential.
Why now: As teams connect agents to business data, they need shared metric definitions and access rules across agent and conventional analytics interfaces.
Implication: Teams can evaluate a governed multi-protocol semantic model as a way to reuse established metric logic and permissions for agent workflows. This is an architectural option, not proof that every agent query will be correct or that the setup is simpler in every environment.
Evidence boundary: The supplied AWS source is a technical walkthrough, not an independent security assessment, benchmark, production outcome, or comparative evaluation.
Watch condition: Look for production audits of agent queries and tests that row-level access remains correct across user roles.
The example’s architecture makes a distinction that matters in deployment: an agent may plan a query, but a separate data-facing layer defines what that query means and which results its caller can see. AgentCore hosts the Strands agent and manages its outbound credential, while AtScale supplies shared business definitions and applies controls when a query runs. The source does not establish how this arrangement performs across workloads or whether it reduces operational effort. The next useful evidence would come from production use: query audits, role-based access tests, and confirmation that agents and BI users continue to receive consistent metric definitions.