I built a self-hosted MCP control layer for enterprise systems — permissions, audit, human-in-the-loop

Description and use

A self‑hosted MCP control layer for enterprise systems that provides per‑dataset access control, audit trails, and human‑in‑the‑loop approval gates, deployed via Docker Compose on the intranet.

Problem

Clients needed a consistent way to control what agents could see, how they accessed systems, and who approved actions, without hand‑rolled solutions per project.

Outcome

The solution provides a unified, self‑hosted control layer that standardizes permissions, audit, and approval across enterprise systems, eliminating custom hand‑rolled implementations.

Workflow

• Deploy the Docker Compose stack on the intranet
• Configure per‑dataset access rules to define who sees what and mask sensitive fields
• Use the plugin engine to generate connectors from templates for target systems
• Enable audit logging to capture every call and trace actions
• Set up human‑in‑the‑loop gates for critical actions to require approval before execution

Evidence

a self-hosted MCP control layer. It exposes your enterprise systems as MCP tools and puts permissions, audit and approval gates on top of them.

Source

Per-dataset access control — configurable who-sees-what, sensitive fields auto-masked

Source

Full audit trail — every call logged and traceable

Source

Human-in-the-loop — critical actions are reviewed before they execute

Source

Docker Compose, runs fully on your intranet — data never leaves your network

Source