For Platform & Engineering Teams

MCP is the wire. We are the policy and audit layer on top.

Plug Claude Code, Codex CLI, Hermes-agent, or Claude Desktop into our Control Plane MCP server. Every tool call passes through a policy gate (allow / deny / HITL / DLP). Audit chain on by default. Self-evolving system prompts via approved Genes — your team's prompts improve themselves, you stay in the loop on every change.

The integration in one block of JSON

This is what a customer adds to their Claude Code (or Codex, or Hermes) MCP server config. Cmd-Q the host, paste the block, relaunch. Tool calls now route through the policy gate and into the audit chain. No code on your side.

// ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai-gov-control-plane": {
      "command": "/path/to/python",
      "args": ["-m", "app.services.control_plane.mcp_server"],
      "cwd":  "/path/to/proofpane/backend",
      "env": {
        "CP_PRINCIPAL": "you@your-co.com",
        "CP_AGENT_ID":  "code_agent.v1",
        "CP_VENDOR":    "claude_code",
        "CP_ORG_ID":    "org_yourco",
        "CP_HITL_TIMEOUT_S": "600",
        "PYTHONPATH":   "/path/to/proofpane/backend"
      }
    }
  }
}

Full template + Codex / Hermes variants: backend/app/services/control_plane/MCP_DESKTOP_CONFIG.md

What the audit log looks like

Hash-chained. One event per tool call, decision, HITL checkpoint, redaction. org_id in the chain hash so cross-org tampering is structurally detectable. Every event has a parent_run_id so the run tree is navigable in the UI.

{
  "event_type": "cp.tool.deny",
  "actor": "code_agent.v1",
  "payload": {
    "tool": "gov_bash",
    "args": { "bash_command": "kubectl delete pod payments-7" },
    "decision": "deny",
    "rule_id": "requires_approval::gov_bash::kubectl",
    "rationale": "destructive op against shared infra; not approved",
    "session_id": "cp_sess_8a4f1e",
    "vendor": "claude_code",
    "policy_eval_ms": 12,
    "chain_prev_hash": "5d3a...",
    "chain_hash":      "9e72..."
  }
}

Why engineering teams pick us

The features above are the surface. These three are the substrate — what holds up when you scale past one team or one agent vendor.