> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corridor.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Governance

> Enterprise visibility and control for AI coding agents through telemetry, inventory, and on-device policy enforcement.

Agent Governance gives Enterprise security teams visibility into agent activity and installed software, along with control over what agents can do. It covers tools, MCP calls, shell commands, skills, and plugins that would otherwise run mostly outside the security team's view.

## Features

| Capability                                                         | Description                                                                                                                              |
| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| [Agent Telemetry & Timeline](/agent-governance/telemetry)          | A searchable stream of agent events, with analytics and per-session views of tool calls, MCP usage, shell commands, skills, and sessions |
| [Artifact Inventory](/agent-governance/artifact-inventory)         | A team-wide catalog of installed MCP servers, Agent Skills, hooks, harness plugins, and editor extensions, with secret scanning          |
| [MCP Tool Controls](/agent-governance/mcp-tool-controls)           | Allow/block policy for MCP servers and their tools                                                                                       |
| [Shell Command Controls](/agent-governance/shell-command-controls) | A deny-list for agent shell commands, including pattern-based rules                                                                      |

## Observability and control

Telemetry and inventory give security teams a shared view of agent activity and installed software. MCP and shell policies run on the developer's device, inside Corridor's agent hooks, before an action executes.

These controls are designed to stop a cooperating agent from taking an action your team has ruled out. When a control cannot evaluate an action, it fails open so it does not block development.

## Supported agents

Corridor delivers Agent Governance through hooks installed by the [Corridor CLI](/getting-started/quickstart) or IDE extension:

| Capability             | Cursor | Claude Code | OpenAI Codex | Factory Droid | Devin Desktop |
| ---------------------- | :----: | :---------: | :----------: | :-----------: | :-----------: |
| Agent Telemetry        |    ✓   |      ✓      |       ✓      |       ✓       |       ✓       |
| Artifact Inventory     |    ✓   |      ✓      |       ✓      |       —       |       —       |
| MCP Tool Controls      |    ✓   |      ✓      |       ✓      |       ✓       |       ✓       |
| Shell Command Controls |    ✓   |      ✓      |       ✓      |       ✓       |       ✓       |

✓ means the capability is supported when Agent Governance is enabled for the team.

The Artifact Inventory row covers coding-agent configuration. Editor-extension inventory also covers the VS Code family and JetBrains IDEs, regardless of which coding agent is in use. GitHub Copilot has no hook interface, so these capabilities do not cover it.

<Note>
  Agent Governance is rolling out to Enterprise teams. If you don't see these pages in your dashboard yet, contact [support@corridor.dev](mailto:support@corridor.dev) or your Corridor representative.
</Note>

## Availability and enablement

* Agent Governance is available on the **Enterprise** plan, including Enterprise trials.
* In **Team Settings → Agent Observability**, the **Agent Telemetry** and **Artifact Inventory** toggles control what Corridor collects from your developers' machines. Turning a stream off makes the server drop incoming data and connected clients stop sending it. Only team **Owners** can change these settings.
* Governance dashboards, including Agent Sessions, are visible to team **Owners** and **Admins**.
* Only team **Owners** can change MCP and shell rules.

## Where to find it

Open **Governance** in the Corridor dashboard:

* **Analytics**: Tool Call Analytics
* **Timeline**: the event stream, session list, and shell usage views
* **Agent Sessions**: the per-conversation session browser
* **Inventory**: the artifact catalog, with an All view and separate MCP, Skills, Hooks, Plugins, and Extensions views
* **MCP**: MCP server and tool policy
* **Shell Controls**: shell command rules

## Next steps

<CardGroup cols={2}>
  <Card title="Agent Telemetry & Timeline" icon="wave-pulse" href="/agent-governance/telemetry">
    See what your agents are doing
  </Card>

  <Card title="Artifact Inventory" icon="boxes-stacked" href="/agent-governance/artifact-inventory">
    See what's installed across your team
  </Card>

  <Card title="MCP Tool Controls" icon="plug" href="/agent-governance/mcp-tool-controls">
    Set allow/block policy by server and tool
  </Card>
</CardGroup>