FINOS AI Governance MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

List Mitigations

list_mitigations

Lists AI governance mitigation documents with security controls, privacy safeguards, and implementation guidance to help reduce AI risks and address compliance needs.

Instructions

List all available AI governance mitigation strategies for risk reduction and security controls.

Use this tool to discover security controls, privacy safeguards, and compliance measures for AI systems. Each mitigation document provides actionable controls, implementation guidance, and best practices for reducing identified risks and threats.

Each entry is named and described by the document itself, so this reads every document in the catalog rather than only the file listing -- one cached fetch per document. A document that cannot be read keeps a name derived from its filename and has no description, so the listing is always complete.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_mitigations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`source`	Yes
`documents`	Yes
`total_count`	Yes
`document_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it discloses that the tool reads every document in the catalog with one cached fetch per document (a real cost signal), and that unreadable documents fall back to a filename-derived name with no description so the listing is always complete. It omits permission/auth requirements and explicit read-only framing, keeping it at a 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then usage, then operational caveats — a sensible ordering with no redundant sentences. The middle sentence's list of document contents ("actionable controls, implementation guidance, and best practices") is mild filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description still covers cost behavior and partial-failure semantics. An agent has what it needs to call it; only access/permission preconditions are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline is 4. The description correctly implies a full-catalog, unfiltered listing, which matches the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List all available AI governance mitigation strategies") and scopes the content to risk reduction and security controls, which distinguishes it in substance from list_risks and list_frameworks. It does not explicitly name a sibling it is not, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use: "Use this tool to discover security controls, privacy safeguards, and compliance measures for AI systems." It does not state when not to use it or point to get_mitigation for retrieving a single document, so no exclusions or alternatives are offered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server