# 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.

## Policies in this guide

- [Fence Glean Search by Datasource](https://www.intentbasedpolicy.com/policies/glean/fence-datasource-scope) — Glean's search tool fans out across every system the tenant has indexed (Drive, Confluence, Slack, Jira, Gmail/Outlook, GitHub, Salesforce, Gong, HR…
- [Cap Glean Bulk Search Export](https://www.intentbasedpolicy.com/policies/glean/cap-search-export) — Clamps the bulk-export parameters on Glean search calls before they reach the Glean MCP server, so a single agent request cannot pull an entire indexed…
- [Glean: Redact PII from Read-Tool Responses](https://www.intentbasedpolicy.com/policies/glean/redact-pii-egress) — Scans the responses of Glean's content-returning read tools and rewrites high-confidence PII to fixed redaction tokens before the response reaches the…
- [Glean Default-Deny Unknown Tools](https://www.intentbasedpolicy.com/policies/glean/default-deny-unknown-tools) — Pins a per-tenant allowlist of the verified built-in read tools on the Glean managed remote MCP server and denies every other tool suffix on the Glean server…
