> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance.md).

# AI Governance

### AI Governance

As employees adopt AI coding assistants like Claude Code, Cursor, and GitHub Copilot, those assistants increasingly reach beyond the editor, connecting to external tools and data sources through the **Model Context Protocol (MCP)**, running shell commands, and reading from your codebase and filesystem. Each of these actions is a potential path for sensitive data to leave your environment, often invisibly to traditional DLP. Nightfall's AI Agent Governance gives security teams **visibility into what AI agents are doing** and the ability to **apply data protection policies to that activity in real time**.

This section covers three surfaces in the Nightfall console under **AI Governance**:

* **MCP Server Visibility** (Inventory, Collections, Users & Devices, Settings): what is already running on endpoints
* **MCP Gateway**: the governed endpoint for servers you enable, with credentials and an audit log
* **Auditability and Control**: hooks, OpenTelemetry, and AI agent security policies

#### MCP Server Visibility

The Model Context Protocol lets AI assistants connect to external servers that provide tools and data, for example a GitHub server, a database connector, or an internal knowledge base. Because these connections can move data in and out of the assistant, knowing **which servers are in use** is the foundation of governing them.

Nightfall automatically discovers and reports MCP activity across your monitored endpoints:

* **Connected servers and clients** - Nightfall detects the MCP servers each AI client connects to and surfaces these as connection events in the **AI Governance** dashboard.
* **Configuration discovery** - MCP server configurations are discovered from the agent's settings on the endpoint, including assistants installed through managed channels such as the Microsoft Store.
* **Accurate client attribution** - Each event is attributed to the specific assistant that generated it (for example, Claude Code or Claude Desktop).

> *Note:* Some AI clients label MCP tool activity differently, and a few do not include the server name in the activity they report. Where the server can be identified, you can scope policies to specific servers; where it cannot, that activity is governed under your broader "all servers" policies.

#### MCP Gateway

MCP Gateway is a separate tab next to Inventory. Clients such as Cursor, Claude Code, Windsurf, and VS Code connect to one Nightfall endpoint. Admins enable servers from a catalog or by URL. Users bring their own OAuth or PAT. Every tool call is written to the gateway Audit log.

The gateway tab is enabled per organization. If you do not see it, contact your Nightfall account team.

#### New capabilities via Hooks and OpenTelemetry

Beyond seeing which servers are connected, Nightfall can inspect and act on what AI agents actually do: the prompts, tool calls, and responses flowing through them.

* **Hooks** - lifecycle hooks that fire as the agent works. Nightfall uses them to inspect activity and enforce policy.
* **OpenTelemetry (OTel)** - structured agent telemetry that feeds the same dashboards and detection policies you use across Nightfall.

### MCP Server Visibility

### MCP Gateway

### Auditability and Control


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
