AINumbers Fintech Intelligence Suite

NIST AI RMF Function Mapper

map_nist_ai_rmf_functions

Read-onlyIdempotent

NIST AI RMF Function Mapper: OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Output feeds: art-175-gpai-code-of-practice-conformance, art-314-traiga-safe-harbor-pack-builder. Open at: https://ainumbers.co/chaingraph/art-174-nist-ai-rmf-function-mapper.html FV-status (published/proven/still-trusted for this spec): /fv-status/ca4e1dca8343f788a296161f0e19712f7afb7e5eaec0431081e715a4cc34b784.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Map supplied AI controls and evidence to NIST AI RMF Govern (5 controls), Map (4), Measure (4), and Manage (4) functions: 17 controls total. Outputs: all_gaps, controls_present, coverage_band, function_coverage, overall_coverage, total_controls. Output schema: call describe_tool("map_nist_ai_rmf_functions").

Input Schema

Name	Required	Description
`compute`	No	Compute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
`parent_hashes`	No	execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
`parent_tool_ids`	No	tool_id values matching parent_hashes, in the same order.
`policy_parameters`	No	Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / policy_parameters / description

Previous value: -"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". See the tool's manifest for field names."New value: +"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". Unknown keys are refused."

addedInput schema / properties / policy_parameters / properties
```
Added value: +{
+  "evidence": {}
+}
```
removedInput schema / properties / policy_parameters / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "all_gaps": {
-      "type": "array"
-    },
-    "controls_present": {
-      "type": "integer"
-    },
-    "coverage_band": {
-      "type": "string"
-    },
-    "function_coverage": {
-      "properties": {
-        "GOVERN": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        },
-        "MANAGE": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        },
-        "MAP": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        },
-        "MEASURE": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        }
-      },
-      "type": "object"
-    },
-    "overall_coverage": {
-      "type": "integer"
-    },
-    "total_controls": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "all_gaps": {
+      "type": "array"
+    },
+    "controls_present": {
+      "type": "integer"
+    },
+    "coverage_band": {
+      "type": "string"
+    },
+    "function_coverage": {
+      "properties": {
+        "GOVERN": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "MANAGE": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "MAP": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "MEASURE": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "overall_coverage": {
+      "type": "integer"
+    },
+    "total_controls": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedJun 27, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the annotations, the description explains compute modes, server-side versus browser delegation behavior, transient input processing, the synthetic/anonymised input requirement, AP2 artifact export with execution_hash, and downstream artifact feeds. It does not contradict the read-only annotations and adds meaningful operational context.

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

Conciseness2/5

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

The description is heavily bloated with OpenChainGraph boilerplate, FV-status receipt details, URLs, and provenance language before reaching the actual mapping purpose. The useful summary and output list are present but not front-loaded, and several sentences do not help an agent select or invoke the tool.

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?

For a complex mapping tool with no output schema, the description gives the core purpose, output fields, compute/provenance behavior, and privacy constraints. It still lacks explicit routing guidance against sibling tools, but an agent has enough information to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains compute, parent_hashes, parent_tool_ids, and policy_parameters. The description adds some context via compute-mode behavior and synthetic-input guidance, but it mostly repeats or loosely references what the schema already documents.

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?

The summary states a specific verb and resource: map supplied AI controls and evidence to NIST AI RMF Govern, Map, Measure, and Manage functions, with 17 controls total. It is clearly distinguishable from generic governance-fit siblings, though the purpose is buried after OpenChainGraph compute-node boilerplate.

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

Usage Guidelines3/5

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

The description implies when to use the tool by naming the NIST AI RMF mapping task and listing outputs, but it never explicitly states when to choose it over related AI governance or conformance siblings. No alternatives or exclusions are given.

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

All AINumbers Fintech Intelligence Suite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

NIST AI RMF Function Mapper

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources