AI Governance Institute
← News
Insight2026-06-13

AI Governance Institute Publishes Open-Source MCP Server for Automating Governance Controls

Source

ai-governance-mcp on GitHub

AI Governance Institute

What happened

AI Governance Institute published the ai-governance-mcp server to GitHub under an open-source license. The server exposes three governance controls as MCP tools: one runs output guardrail checks against a system prompt or model output and flags policy violations; one scores an AI deployment against a structured risk taxonomy and returns a risk tier with justification; and one generates adversarial test cases for a target system prompt and summarizes attack surface findings. All three tools run locally through Claude Code or any client that supports the Model Context Protocol.

Why it matters

  • ·Governance controls have historically lived in policy documents, not in developer workflows. MCP tooling changes that: when safety screening and risk classification run inside the same environment where AI systems are built and tested, teams can catch governance gaps at the point of development rather than after deployment. The friction of running a governance check drops from hours to seconds.
  • ·The three controls chosen for the initial release (SAF-001, HOC-001, SAF-005) cover the highest-value automation opportunities: output validation, risk tier assignment, and adversarial testing. These are also the controls most often skipped in practice because they require specialized effort to run consistently. Automating them via MCP removes the effort barrier.
  • ·MCP is emerging as the standard integration layer for AI tooling. Publishing governance controls as MCP tools means they can be composed with other tools in agentic workflows, not just used interactively. A CI/CD pipeline, an agent review step, or a pre-deployment checklist can all invoke these controls programmatically.
  • ·Open-source distribution allows compliance teams to inspect the control logic, adapt it to their internal risk taxonomy, and contribute improvements. Governance tools that are opaque or proprietary are harder to audit and harder to trust. Reviewable source is a prerequisite for controls that produce audit-ready output.

Governance controls affected

SAF-001Hallucination Detection and MitigationSAF-005Harmful Content FilteringHOC-001AI System Risk Classification

What to do now

  • ☐Install the ai-governance-mcp server and add it to your Claude Code MCP configuration to start running safety screening and risk classification in your development workflow.
  • ☐Run the risk classification tool against any AI systems currently in development or recently deployed to get a baseline risk tier. Compare the output against your internal risk register and flag discrepancies for review.
  • ☐Use the red-teaming tool to generate adversarial test cases for any system prompts powering customer-facing or high-stakes internal AI applications. Review the attack surface summary with your security team before go-live.
  • ☐If your organization has a custom risk taxonomy, consider forking the repository and adapting the risk classification logic to align with your internal definitions. The control logic is designed to be readable and modifiable.
  • ☐Review your AI governance program for other controls that could be automated and flag them for future MCP tool development. Controls with structured inputs and verifiable outputs are the best candidates.

What to watch next

Additional governance controls moving toward automation in the Control Executor roadmap, and whether the MCP ecosystem develops shared schemas for governance tool output so that results from different tools and vendors can be aggregated into a unified compliance record.

Stay ahead of stories like this

Get every Global AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Free every Thursday. Unsubscribe anytime.

Related Coverage

Enforcement2026-09-30

SBA's AI Fraud Pilot Never Classified as High-Impact, OIG Finds

The SBA's Office of Inspector General found that a Palantir-powered AI fraud detection pilot for COVID-19 loan programs was never classified as a high-impact use case under OMB guidance. As a result, required safeguards including impact assessments, human oversight mechanisms, and borrower appeals processes were never put in place. The OIG issued six recommendations, including establishing a formal process for identifying and documenting high-impact AI use cases.

Enforcement2026-10-10

ICO Opens Formal Grok Investigation Into Data Processing and Harmful Synthetic Images

The UK Information Commissioner's Office has opened formal investigations into X Internet Unlimited Company and X.AI LLC. The probe covers how Grok processes personal data and its capacity to generate harmful sexualized synthetic images and videos. Enterprise teams should treat the case as an enforcement signal for any AI system capable of generating synthetic media involving real people.

Research2026-10-09

Google, JPMorgan, and Two Governments Exposed by Recurring MCP Server Flaw

Security researchers found a recurring vulnerability in MCP (Model Context Protocol) servers run by Google, JPMorgan Chase, Weaviate, France's DINUM, and Tangerang City. The flaw lets AI agents manipulate outbound network requests and relay malicious instructions to other agents. It exposes a structural gap in how organizations deploy the protocol that connects AI agents to external systems. Researchers recommend destination validation, network isolation, and explicit authorization controls for inter-agent transactions.