ai-governance-controls

ai_risk_classify

Evaluate an AI deployment description to classify its risk tier and applicable regulations using HOC-001, EU AI Act, and NIST AI RMF frameworks.

Instructions

Classify an AI deployment's risk tier and applicable regulations (HOC-001).

Evaluates a deployment description against the HOC-001 risk classification control, referencing EU AI Act risk tiers and NIST AI RMF. Returns a structured analysis framework for the host to complete.

Args: deployment_description: Description of the AI system and how it is deployed. Include: what the system does, who uses it, what decisions it influences, what data it processes, and any human oversight in place.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deployment_description": "<deployment_description>"
    },
    "name": "ai_risk_classify"
  }
}

Input Schema

Name	Required	Description	Default
`deployment_description`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Describes the evaluation process and references regulations, and notes the return is a 'structured analysis framework for the host to complete,' implying interactive use. No annotations are present, so the description carries the full burden but does not disclose all behavioral traits (e.g., side effects, auth requirements).

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?

The description is well-structured with a clear purpose statement, explanation of the evaluation framework, and an Args section. It is reasonably concise for the complexity, though some sentences could be tightened.

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?

Given the single parameter and presence of an output schema, the description provides adequate context for the tool's purpose and input. The notion of a 'structured analysis framework' is somewhat vague, but sufficient for an agent to understand the tool's role.

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?

With 0% schema description coverage, the description compensates by providing detailed guidance on what to include in the deployment_description parameter (system purpose, users, decisions, data, oversight). This adds significant meaning beyond the schema's basic type and title.

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?

Clearly states it classifies risk tier and applicable regulations for an AI deployment, referencing specific controls (HOC-001, EU AI Act, NIST AI RMF). Does not explicitly differentiate from sibling tools like ai_red_team and ai_safety_screen, but the distinct purpose is evident.

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?

Provides guidance on when to use (evaluating deployment description against HOC-001) and what to include in the description. Lacks explicit when-not-to-use examples or alternatives, though the context of siblings might imply they are for different tasks.

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

Deploy Server