See AI access that needs review.
Discovery ingests network observations, correlates coverage gaps, and combines them with connected-app and tool inventories. These paths are implemented; their coverage depends on deployed observers, connector permissions, and SDK instrumentation.
Built · development scope Discovery Agent, reviewed 19 October 2026. Observed activity is evidence to review, not automatic enforcement.
Example · illustrative data
Discovery inventory: three evidence sources
- Nightly sync helper
- Network metadata shows a known AI destination.
- Flagged
- Chat tool grant
- Connector reports a broad mailbox scope.
- Flagged
- SDK tool candidate
- Observed tool registered after human review.
- Registered
Review evidence before changing access or routing.
Passive network observations
The Linux observer reads connection metadata and matches remote IPs against DNS-resolved known AI hosts. Enrollment binds reports to a tenant; the backend creates or updates connected apps and coverage gaps and correlates them with other evidence.
Deployment manifests cover Kubernetes and a host-process mode. The passive observer does not block or redirect traffic. Shared IPs, DNS changes, unknown hosts, and the observer's installation boundary limit what it can see.
Network metadata does not establish the exact data read, the full OAuth permissions, or whether a human approved the activity. A separate, gated TLS proxy can report HTTP method and path structure; it requires its own deployment and trust setup.
Connected apps and tool candidates
Configured connectors synchronize app and grant metadata. Risk scoring flags selected broad scopes and AI-related apps for review. SDK monitor events also produce tool-discovery candidates, with observed and simulated evidence distinguished.
A security engineer can register a discovered tool in the registry or dismiss the candidate. Registering a tool does not route its traffic through the gateway or automatically supply a new agent identity and policy.
Connector permissions and upstream APIs determine which grants are visible. The inventory does not infer the minimum permissions a particular business task actually needs.
From observation to an enforced route
Coverage gaps have review states, notes, and remediation actions. Accepting a risk or changing a finding's state records a review decision; it does not by itself interpose the gateway.
- Observe. Collect network, connector, or SDK evidence within the configured boundary.
- Review. Inspect the source and confidence; record a decision on the gap or candidate.
- Configure. Register the agent and tool, route calls through an SDK guard or MCP proxy, and select policy.
- Verify. Confirm actual routed calls and enforcement behavior. Monitor telemetry alone does not prove enforcement.
Start with a known boundary
Review connector coverage, routed enforcement paths, and current status. Discuss an installation through contact.