ISMS Copilot Docs

GDPR DPIA necessity checker: free MCP tool

Call the GDPR DPIA necessity checker from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.

gdpr_dpia_necessity 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.

Reads whether a processing operation likely needs a data protection impact assessment under GDPR Article 35, using the nine criteria of the WP248 guidelines, with the reasons. Answer every question (the input schema lists them with their options); with any question unanswered the tool returns the open questions instead of a verdict. The verdict is a reading from fixed rules, not a legal conclusion. 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 GDPR DPIA necessity checker page.

Inputs

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

FieldWhat it isAllowed values
answersOne answer per question, keyed by question id. Every question needs an answer before a verdict is computed.object (fields below)
answers.evaluationScoringDo you evaluate or score people, including profiling or predicting their behaviour, performance, interests, health, or movements? Examples: credit or fraud scoring, behavioural advertising profiles, performance ranking, health or location prediction.yes (Yes), no (No)
answers.automatedDecisionsDo you make automated decisions that produce legal effects or similarly significantly affect people, with little or no human involvement? Examples: automated loan refusals, automated hiring rejections, eligibility decided by an algorithm.yes (Yes), no (No)
answers.systematicMonitoringDo you systematically monitor people, including monitoring of publicly accessible areas? Examples: CCTV of public spaces, location or behaviour tracking, network or employee monitoring.yes (Yes), no (No)
answers.sensitiveDataDo you process sensitive data or data of a highly personal nature? Examples: health, biometric, genetic, racial or ethnic, religious, political, sex-life, criminal-offence, financial, or location data.yes (Yes), no (No)
answers.largeScaleDo you process personal data on a large scale? Weigh the number of people, the volume and range of data, the duration, and the geographic extent. One GP's patient records is not large scale; a hospital network's is.yes (Yes), no (No)
answers.matchingCombiningDo you match or combine datasets, for example from different operations or sources, in a way data subjects would not expect? Examples: merging data from several services, enriching profiles with third-party data.yes (Yes), no (No)
answers.vulnerableSubjectsDo you process data about vulnerable people, where there is a power imbalance? Examples: children, employees, patients, asylum seekers, the elderly.yes (Yes), no (No)
answers.innovativeTechDo you use innovative technology or apply new technological or organisational solutions? Examples: AI, facial or biometric recognition, IoT devices, combining new identification methods.yes (Yes), no (No)
answers.preventsRightOrServiceDoes the processing itself prevent people from exercising a right or using a service or a contract? Example: a screening database that determines who is offered a loan, an account, or a contract.yes (Yes), no (No)

If an answer is missing

The tool never guesses an answer. A call with any field left out returns status: "needs_answers" and the open questions, each with its id, its text and its allowed values, and no result. Your AI can ask you those questions and call again.

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": "gdpr_dpia_necessity",
    "arguments": {
      "answers": {
        "evaluationScoring": "yes",
        "automatedDecisions": "no",
        "systematicMonitoring": "no",
        "sensitiveData": "yes",
        "largeScale": "yes",
        "matchingCombining": "no",
        "vulnerableSubjects": "no",
        "innovativeTech": "no",
        "preventsRightOrService": "no"
      }
    }
  }
}

Response

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

{
  "status": "result",
  "verdict": {
    "id": "likely-required",
    "reading": "Reading from fixed rules, not a legal conclusion: A DPIA is likely required",
    "page_title": "A DPIA is likely required",
    "summary": "Your processing meets two or more of the EDPB criteria, which indicates it is likely to result in a high risk to people's rights and freedoms. The EDPB guidance says a DPIA should be carried out in that case. Do it before the processing starts and involve your DPO. If one of the conditions noted below applies, the processing may also fall within a presumptively mandatory case under Article 35(3).",
    "tone": "in"
  },
  "reasons": [
    {
      "code": "art35-3b-possible",
      "text": "Possible Article 35(3)(b) case: if the large-scale data includes special-category data (Article 9) or criminal-offence data (Article 10) specifically, a DPIA is presumptively mandatory. Confirm the data categories with your DPO."
    },
    {
      "code": "two-or-more",
      "text": "You met two or more of the nine EDPB criteria, the threshold the EDPB uses to indicate processing likely to result in a high risk."
    },
    {
      "code": "criterion-evaluationScoring",
      "text": "Met: evaluation or scoring (including profiling and prediction)."
    },
    {
      "code": "criterion-sensitiveData",
      "text": "Met: sensitive data or data of a highly personal nature."
    },
    {
      "code": "criterion-largeScale",
      "text": "Met: processing on a large scale."
    },
    {
      "code": "dpa-lists",
      "text": "Your supervisory authority publishes its own list of processing that always requires a DPIA (Article 35(4)) and may publish a list that does not (Article 35(5)). These vary by Member State and take precedence over this rule of thumb, so check them."
    }
  ],
  "obligations": [
    "A systematic description of the processing operations and their purposes.",
    "An assessment of whether the processing is necessary and proportionate to those purposes.",
    "An assessment of the risks to the rights and freedoms of data subjects.",
    "The measures you will take to address those risks: safeguards, security measures, and mechanisms to demonstrate compliance.",
    "Related steps (not part of Article 35(7) itself): seek the advice of your DPO (Article 35(2)), and where a high residual risk remains, consult your supervisory authority before processing (Article 36)."
  ],
  "answered": 9,
  "total": 9,
  "basis": [
    "GDPR Article 35",
    "WP248 rev.01 (endorsed by the EDPB)"
  ],
  "sources_checked_on": [
    {
      "source": "Regulation (EU) 2016/679 (GDPR), Article 35 (EUR-Lex)",
      "checked_on": "2026-07-17"
    },
    {
      "source": "Article 29 Working Party Guidelines on Data Protection Impact Assessment, WP248 rev.01 (endorsed by the EDPB)",
      "checked_on": "2026-07-17"
    }
  ],
  "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-gdpr-dpia-necessity-checker",
    "label": "Review your own documents against this framework with ISMS Copilot"
  },
  "tool_page": "https://www.ismscopilot.com/resources/gdpr-dpia-necessity-checker"
}

What the result rests on

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

  • GDPR Article 35
  • WP248 rev.01 (endorsed by the EDPB)

Sources the rules were checked against, with the date each was last checked:

  • Regulation (EU) 2016/679 (GDPR), Article 35 (EUR-Lex), checked 2026-07-17
  • Article 29 Working Party Guidelines on Data Protection Impact Assessment, WP248 rev.01 (endorsed by the EDPB), checked 2026-07-17

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