GDPR data processing agreement checker: free MCP tool
Call the GDPR data processing agreement 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_dpa_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 relationship likely needs an Article 28 data processing agreement, an Article 26 joint-controller arrangement, or neither under the GDPR, with the reasons and the contract points to cover. 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 data processing agreement checker page.
Inputs
The tool's input schema, as tools/list returns it, field by field.
| Field | What it is | Allowed values |
|---|---|---|
answers | One answer per question, keyed by question id. Every question needs an answer before a verdict is computed. | object (fields below) |
answers.involvesPersonalData | Does this arrangement involve personal data? Personal data is any information relating to an identified or identifiable living person: names, emails, IDs, location, online identifiers, and so on. If no personal data changes hands, Article 28 does not engage and no DPA is needed for data-protection reasons. | yes (Yes), no (No) |
answers.relationship | How do the two organisations relate to the personal data in this arrangement? This is the decisive question. A processor handles data only on another organisation's behalf and instructions. Independent controllers each pursue their own purposes with the same data. Joint controllers decide the why and how together. Pick the closest fit; if it is genuinely unclear, choose the last option. | one-processes-for-other (One organisation processes the data only on behalf of, and on the instructions of, the other (for example a SaaS vendor, payroll bureau, or hosting provider handling data for a customer).), each-own-purposes (Each organisation independently decides its own purposes for the data (for example two businesses that each use the shared data for their own separate aims).), jointly-decide (The two organisations jointly decide why and how the data is processed (a shared purpose, shaping the means together).), unsure (It is not yet clear which of these describes the arrangement.) |
answers.yourRole | In this arrangement, which side is your organisation on? This tailors the obligations the result highlights. A controller decides why and how the data is processed. A processor acts on a controller's behalf and instructions. If you are not sure, choose the last option. | controller (We are the controller (the data and its purposes are ours; the other party serves us).), processor (We are the processor (we handle the data on the other party's behalf and instructions).), unsure (Not sure.) |
answers.processorOnInstructionsOnly | Where one party processes on the other's behalf, will it act only on that other party's documented instructions, and not use the data for its own purposes? A genuine processor sticks to the controller's documented instructions. If the party handling the data also uses it to pursue its own purposes, it is acting as a controller for that processing, whatever the contract calls it (Article 28(10)). Answer for the processing-on-behalf relationship; if there is none, this does not change the result. | yes (Yes), no (No) |
answers.engagingSubprocessor | Will the party that processes on the other's behalf bring in a further organisation (a sub-processor) to help carry out that processing? A processor may only engage a sub-processor with the controller's authorisation, and must impose the same data-protection obligations on it by contract (Article 28(2) and 28(4)). Examples of sub-processors: a cloud host, an email-delivery service, or an offshore support team used to deliver the service. | yes (Yes), no (No) |
answers.internationalTransfer | Will the processing involve transferring the personal data outside the EU/EEA? If the data is sent to, stored in, or accessible from a country outside the EU/EEA, Chapter V transfer rules apply on top of whatever contract the relationship needs. This does not change whether you need a DPA; it adds a separate obligation. Our Cloud Act and Schrems II analyzer assesses transfer exposure in detail. | 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_dpa_necessity",
"arguments": {
"answers": {
"involvesPersonalData": "yes",
"relationship": "one-processes-for-other",
"yourRole": "controller",
"processorOnInstructionsOnly": "yes",
"engagingSubprocessor": "no",
"internationalTransfer": "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": "dpa-required",
"reading": "Reading from fixed rules, not a legal conclusion: You need a data processing agreement (Article 28 contract)",
"page_title": "You need a data processing agreement (Article 28 contract)",
"summary": "On your answers this is a controller-processor relationship: one party processes personal data on behalf of, and on the documented instructions of, the other. Article 28(3) requires that this be governed by a written contract (a DPA) covering the mandatory content below, and Article 28(1) requires the controller to use only processors that give sufficient guarantees of GDPR-compliant processing. Put the DPA in place before the processing starts. If a sub-processor is involved, an equivalent Article 28(4) contract is needed down the chain.",
"tone": "in"
},
"reasons": [
{
"code": "controller-processor",
"text": "You indicated one party processes the data on behalf of, and on the instructions of, the other. That is a controller-processor relationship under Article 28."
},
{
"code": "art28-required",
"text": "Article 28(3) requires the processing to be governed by a written contract (a DPA) that identifies what processing is covered, how long it lasts, why and how it is performed, the types of personal data and categories of data subjects involved, and the rights and duties the controller keeps, and that includes the mandatory content listed on this page."
},
{
"code": "controller-duties-28-1",
"text": "As the controller, you must use only processors that provide sufficient guarantees to implement appropriate technical and organisational measures (Article 28(1)), and adherence to an approved code of conduct or certification can help evidence those guarantees (Article 28(5))."
},
{
"code": "role-is-functional",
"text": "Roles under the GDPR are functional and fact-based: a controller decides the purposes and means of processing (Article 4(7)), a processor acts on a controller's behalf and instructions (Article 4(8)). The label in a contract does not settle the role (Article 28(10), EDPB Guidelines 07/2020)."
}
],
"obligations": [
"Process the personal data only on the controller's documented instructions, including for any transfer outside the EU/EEA, unless required to do otherwise by EU or member-state law; where such a law applies, the processor must inform the controller before processing unless the law prohibits that notice on important public-interest grounds (Article 28(3)(a)).",
"Ensure that people authorised to process the data are bound by an appropriate duty of confidentiality (Article 28(3)(b)).",
"Take all security measures required by Article 32 (Article 28(3)(c)).",
"Respect the conditions for engaging a sub-processor, including the controller's authorisation and an equivalent contract down the chain (Article 28(3)(d), with 28(2) and 28(4)).",
"Help the controller respond to data-subject rights requests, taking the nature of the processing into account (Article 28(3)(e)).",
"Help the controller meet its security, breach-notification, and data-protection-impact-assessment duties under Articles 32 to 36 (Article 28(3)(f)).",
"At the end of the services, delete or return the personal data at the controller's choice, and delete existing copies unless storage is legally required (Article 28(3)(g)).",
"Make available the information needed to demonstrate compliance with Article 28, and allow for and contribute to audits and inspections by the controller or its auditor (Article 28(3)(h)).",
"Record the contract in writing, including in electronic form (Article 28(9)), and require the processor to promptly warn the controller if, in its view, an instruction would breach the GDPR or other applicable EU or member-state data-protection law."
],
"answered": 6,
"total": 6,
"basis": [
"GDPR Articles 4, 26 and 28",
"EDPB Guidelines 07/2020"
],
"sources_checked_on": [
{
"source": "Regulation (EU) 2016/679 (GDPR), Articles 28, 26, and 4 (EUR-Lex)",
"checked_on": "2026-06-07"
},
{
"source": "EDPB Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.0, adopted 7 July 2021",
"checked_on": "2026-06-07"
}
],
"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-dpa-necessity-checker",
"label": "Review your own documents against this framework with ISMS Copilot"
},
"tool_page": "https://www.ismscopilot.com/resources/gdpr-dpa-necessity-checker"
}What the result rests on
Every result names its basis, as identifiers only (never standard text):
- GDPR Articles 4, 26 and 28
- EDPB Guidelines 07/2020
Sources the rules were checked against, with the date each was last checked:
- Regulation (EU) 2016/679 (GDPR), Articles 28, 26, and 4 (EUR-Lex), checked 2026-06-07
- EDPB Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.0, adopted 7 July 2021, checked 2026-06-07
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.