As agents enter work, control spreads across three layers
Updates from MCP, Google Cloud and Wix show how transport, data permissions and output review are being built as separate control layers for business agents.
Artificial Intelligence··Evening
The transport layer learns to identify the request
The MCP 2026-07-28 release reported by InfoQ changes how agent traffic reaches a server. The initialize handshake and Mcp-Session-Id header leave the core request path, while every request carries its required protocol version, client identity and capabilities. Requests can therefore be routed across instances without remaining attached to a server that preserves a particular session. The mandatory Mcp-Method and Mcp-Name headers on Streamable HTTP requests also allow gateways, rate limiters and firewalls to apply rules by method or tool without opening the JSON body. This simplification changes calls that need human input as well: the server returns input_required, the client gathers the answer and resends the call. On authorization, Dynamic Client Registration is deprecated and prepared for removal after summer 2027; the client supplies the canonical server address as the resource so a token is accepted only by its intended server. The same release thus opens a scaling path and puts traffic into a form that ordinary network infrastructure can inspect.[1]
Business data keeps its existing permissions
Google Cloud's route between Looker and Gemini Enterprise builds a second control layer around the meaning of business data and its access permissions. Looker analysts and administrators can publish conversational agents into Gemini Enterprise through the Agent-to-Agent protocol. According to the company, version-controlled business logic generates deterministic SQL instead of leaving an agent to infer joins. Row and column access rules already defined in Looker remain in force along the query path: users without permission for certain rows cannot see them in the agent's answer, and column masking rules are applied in the same way. Google Cloud describes the route as pass-through, saying it neither copies the underlying database nor writes to persistent storage. The announcement mentions Looker release 26.12 on the visualization side. It does not, however, name a customer, provide performance figures or say whether the Gemini Enterprise publishing route is generally available or in preview. The disclosed design therefore offers a concrete architecture for preserving business definitions and permissions, while leaving its deployment outcomes undocumented.[2]
In the small business, the last stop is a person
Wix's newly launched Symphony carries the same search for control into the daily workflow of a small business. In the product, which Wix describes as platform-agnostic, a central agent called Maestro monitors activity and delegates outreach, marketing, scheduling, research, finance and design work to specialists. The launch material also describes a daily morning meeting that presents completed work and opportunities to the owner. A separate layer has another agent review output before it reaches that person. While the MCP release makes methods and tools visible at the gateway, Google Cloud carries business-data permissions into the agent's answer, and Wix establishes task delegation with review before delivery. Together, the developments show that agents enter organizational use through more than a model choice: the transport identifies the call, the data layer limits access, and the application distributes work and checks output. Wix mentions a tiered subscription and a rollout beginning on launch day, but provides no price, independent evaluation or customer outcome. Symphony therefore describes a new control arrangement without yet offering measured evidence of how well it performs.[1], [2], [3]
Related columns
For more information on this topic, you can read the related columns.
