The AWS and Strategy walkthrough offers a concrete instance, not a general proof of the approach.
Observed facts: the example connects a customer-360 model spanning Amazon Redshift and Amazon Aurora to a Strands agent hosted on Amazon Bedrock AgentCore through Strategy Mosaic’s MCP server. Observed facts: the post says joins, metric definitions, and per-caller row and column filters live in Mosaic, and that user identity propagates so those controls apply end to end. It also lists MCP, JDBC/ODBC, XMLA, and REST as interfaces served from the same definition.
The mechanism is that The semantic layer owns business definitions and caller-specific constraints; MCP provides the agent access path, while Mosaic and identity propagation are the stated control point. This is not a claim that MCP itself supplies authorization. This matters now because Teams are connecting agents to governed enterprise data and need boundaries that can serve both agent and conventional clients.
The first implication is that Teams should inspect where metric semantics and authorization are enforced and whether identity survives each hop. The evidence boundary is that This is a vendor-authored implementation walkthrough; it does not independently verify security, performance, or generality beyond the demonstrated setup. The first watch condition is Whether deployments publish reproducible tests showing caller identity, row filters, and metric definitions remain correct across agent requests and non-agent clients.
The story starts a distinct analytical record because no prior New Runtime record was supplied; the source describes a specific semantic-layer/MCP implementation that can be assessed on its own.