Gemini Enterprise for Legal: MCP Permissions Inherit From DMS — Five-Boundary Governance Architecture

Analysis published August 27 by Quasa detailed the permission architecture of Google's Gemini Enterprise for Legal launch, clarifying a question central to KM governance: when Gemini agents access firm knowledge through MCP connectors, which system enforces access controls? The answer is the source DMS. Gemini governs the agent environment; when an agent invokes an MCP connector, the request passes through authentication, the legal system applies its existing user, matter, and document permissions, and only permitted context passes back to the agent. Ethical walls, matter restrictions, and document-level controls in iManage and NetDocuments are not replaced by Gemini's governance layer — they are evaluated by the source platform before any context is returned. For KM teams evaluating Gemini Enterprise, this five-boundary architecture means that the quality of existing permission governance in the DMS determines the quality of AI governance in Gemini — not the other way around.