Govern the one search tool that reaches every system

Enterprise search fans out across everything indexed, so one query can surface what a dozen per-app policies would each have caught. The chokepoint is egress.

For: Security teams deploying Glean or similar enterprise search to agents

Enterprise search is a force multiplier and a governance problem for the same reason: one tool reaches everything the platform has indexed — email, files, tickets, chat, CRM. A single query can pull together what would otherwise be spread across a dozen systems, each with its own access rules. Aggregation amplifies exposure, and the free-text query field means you can't always constrain it on the way in.

That makes egress the real chokepoint. redact-pii-egress masks personal data in results regardless of which source they came from. fence-datasource-scope restricts which indexed datasources the agent may search, keyed to the caller's group. cap-search-export clamps how much a single search returns, throttling bulk harvest. And because a search platform exposes org-built agents and proxied tools with dynamic names, default-deny-unknown-tools denies anything not on the audited list.

One connector that touches everything needs one policy set that assumes exactly that.