ISMS Copilot Docs

Risk register calculator (5x5): free MCP tool

Call the Risk register calculator (5x5) from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.

risk_register_compute is one of the 20 free GRC tools from ISMS Copilot that any AI client can call over MCP: no account, no model, one call.

Scores an information security risk register on a 5x5 likelihood times impact model: inherent score and band per risk, residual score and band when both residual values are given, the count per band and the highest score. Up to 200 risks per call. A starting structure, not a risk method. Returns general information from a fixed rule set; confirm against the official text.

This page is about calling the tool from an AI client: the request, the response and the setup. For the same tool on the web, with the background on the rules it applies, open the Risk register calculator (5x5) page.

Inputs

The tool's input schema, as tools/list returns it, field by field.

FieldWhat it isAllowed values
rowslist of objects (fields below), up to 200
rows[].idYour own id for the risk. Defaults to R1, R2, ... by position.text, up to 40 characters
rows[].assettext, up to 300 characters
rows[].threattext, up to 300 characters
rows[].vulnerabilitytext, up to 300 characters
rows[].likelihood1 (rare) to 5 (almost certain).whole number, 1 to 5
rows[].impact1 (negligible) to 5 (severe).whole number, 1 to 5
rows[].residual_likelihoodAfter treatment. Give it together with residual_impact.whole number, 1 to 5
rows[].residual_impactAfter treatment. Give it together with residual_likelihood.whole number, 1 to 5
rows[].treatmenttext, up to 300 characters

Worked example

This request and response come from the tool itself: the catalog runs the tool's handler on this example input, and this page is generated from that catalog.

Request

A tools/call request, as your client sends it:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "risk_register_compute",
    "arguments": {
      "rows": [
        {
          "asset": "Customer database",
          "threat": "Ransomware",
          "vulnerability": "Backups reachable from the production network",
          "likelihood": 3,
          "impact": 5,
          "residual_likelihood": 2,
          "residual_impact": 4,
          "treatment": "Offline, immutable backups tested monthly"
        },
        {
          "asset": "Staff laptops",
          "threat": "Theft",
          "vulnerability": "Disk encryption not enforced",
          "likelihood": 3,
          "impact": 3
        }
      ]
    }
  }
}

Response

The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.

{
  "status": "result",
  "rows": [
    {
      "id": "R1",
      "asset": "Customer database",
      "threat": "Ransomware",
      "vulnerability": "Backups reachable from the production network",
      "treatment": "Offline, immutable backups tested monthly",
      "inherent": {
        "score": 15,
        "band": "critical"
      },
      "residual": {
        "score": 8,
        "band": "medium"
      }
    },
    {
      "id": "R2",
      "asset": "Staff laptops",
      "threat": "Theft",
      "vulnerability": "Disk encryption not enforced",
      "inherent": {
        "score": 9,
        "band": "medium"
      },
      "residual": null
    }
  ],
  "count": 2,
  "band_counts": {
    "low": 0,
    "medium": 2,
    "high": 0,
    "critical": 0
  },
  "top_score": 9,
  "method": "Score = likelihood x impact, each on a 1 to 5 scale. Bands: 1 to 4 low, 5 to 9 medium, 10 to 14 high, 15 to 25 critical. The effective risk is the residual score when both residual values are given, otherwise the inherent score. A common 5x5 convention, not set by any standard: align it with your own risk method.",
  "basis": [
    "ISO/IEC 27001:2022 clause 6.1.2"
  ],
  "sources_checked_on": [],
  "disclaimer": "General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.",
  "more": {
    "url": "https://www.ismscopilot.com/mcp?ref=mcp-tool-risk-register-starter",
    "label": "Review your own documents against this framework with ISMS Copilot"
  },
  "tool_page": "https://www.ismscopilot.com/resources/risk-register-starter"
}

What the result rests on

Every result names its basis, as identifiers only (never standard text):

  • ISO/IEC 27001:2022 clause 6.1.2

Add the server

claude mcp add --scope user --transport http ismscopilot-free-tools 'https://www.ismscopilot.com/api/public/tools/mcp'

That is Claude Code. For claude.ai, Claude Desktop, ChatGPT, Cursor, Codex and any other client, see Add the server to your client. No sign-in, no token.

Limits

General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.

Your inputs are never logged or stored by our code. We count calls per tool (the tool name, whether it produced a result and when, nothing else). Our host keeps standard request logs (time, path, status, client address) for a short period. Do not send personal data: no tool needs any.

A fixed rule cannot read your own policies, registers or contracts. For a review of your own documents, connect ISMS Copilot, the GRC expert your AI calls.

On this page