Enzai MCP server
Connects to your AI.
Any MCP-compatible agent gets the same governed connection, right where your teams already work.
Some of our integrations
Workflow tools
Jira, ServiceNow
Model providers
Anthropic, OpenAI
Agent tools
Copilot Studio, Claude Enterprise
Development environments
Azure AI Foundry, Amazon Bedrock, Databricks

Glossary

Whitelist/Blacklist Policy

Whitelist/Blacklist Policy

Whitelist/Blacklist Policy

Governance rule defining allowed (whitelist) and disallowed (blacklist) inputs, features, or operations to enforce compliance and prevent misuse.

Governance rule defining allowed (whitelist) and disallowed (blacklist) inputs, features, or operations to enforce compliance and prevent misuse.

Updated

A policy-as-code mechanism where authorized input values, API calls, model operations, or external endpoints are specified in a whitelist, and prohibited items (e.g., PII fields, disallowed functions) are enumerated in a blacklist. During runtime or pipeline execution, policy checks block any unapproved actions. Governance processes maintain and review these lists regularly to adapt to evolving risks and requirements.

Example

A data-ingestion pipeline applies a whitelist/blacklist policy: only CSV files from specified source systems (whitelist) are accepted, and any records containing Social Security numbers (blacklist pattern) are rejected and alerted to compliance. This prevents unauthorized or sensitive data from entering the AI pipeline.

Govern the AI you actually use.

Govern the AI you actually use.

Govern the AI you actually use.

Start with what’s in use.

Start with what’s in use.

Start with what’s in use.

Book a demo and we’ll show you how Enzai finds the AI in use, gives each system an owner and keeps the record.

Book a demo and we’ll show you how Enzai finds the AI in use, gives each system an owner and keeps the record.