Insight2026-06-13

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

Source

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 Mitigation SAF-005Harmful Content Filtering HOC-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.

Jurisdiction

Global

Related Playbook

Is our AI red-teaming rigorous enough? →How do we inventory and classify AI systems by risk level? →How do we govern AI agents that take autonomous actions? →How do we build an AI governance program from scratch? →

Related Coverage

Enforcement2026-08-30

Australia's Fair Work Commission Makes AI Disclosure Mandatory From October 20

Australia's Fair Work Commission issued a cost order against a self-represented litigant who relied on AI-generated legal advice it found 'plain wrong,' and announced a mandatory AI disclosure requirement taking effect October 20, 2026. Commission research links generative AI use to a 40 percent surge in case volume between 2023-24 and 2024-25, with 40 percent of surveyed cases involving an AI-assisted litigant. The disclosure rule is among the first mandatory AI transparency requirements imposed by a labour tribunal and sets a precedent that compliance teams operating across jurisdictions should track closely.

Research2026-08-20

Kriminal Sells Guardrail Bypass for $12.99, Voiding Vendor-Control Assumptions

ThreatDown researchers have identified a clearnet criminal AI service called Kriminal that wraps jailbreak prompts around legitimate models including xAI Grok, Anthropic Claude, Mistral, and Llama 3.3 to resell uncensored capabilities starting at $12.99 per month. The service offers exploit development, OSINT, social engineering, and unrestricted code generation through named agent personas. The finding demonstrates that provider-level safety controls can be systematically circumvented at commodity cost, directly undermining compliance programs that treat upstream guardrails as a primary control.

Corporate Policy2026-08-20

AI Agent Slopsquatting Nearly Plants Malware via Hallucinated Package Name

A software engineer at Softjourn nearly installed a malicious package after an AI agent hallucinated a plausible library name, a technique researchers call slopsquatting. Attackers pre-register packages under names AI models commonly fabricate, turning developer trust into a supply chain attack vector. An existing policy requiring download-count and source-code checks before installing any AI-recommended package prevented the compromise.