CLOUD Act and Schrems II exposure analyzer: free MCP tool
Call the CLOUD Act and Schrems II exposure analyzer from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.
cloud_act_exposure 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 the exposure of EU personal data held with a cloud provider to US government access (CLOUD Act, FISA section 702) after Schrems II, one dimension at a time: provider control, hosting, sub-processors, transfer mechanism, encryption, support access and AI layer. It reports exposure only and by design never says compliant or non-compliant. 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 CLOUD Act and Schrems II exposure analyzer 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.euPersonalData | Does this vendor/service process personal data of people in the EU/EEA? If no personal data subject to the GDPR is involved, a Schrems II transfer assessment is generally not triggered for this vendor. | yes (Yes), no (No), unsure (Unsure) |
answers.providerHq | Where is the legal entity providing the service headquartered? | eu-eea (EU / EEA), adequacy-country (A country with an EU adequacy decision (e.g. UK, Switzerland)), us (United States), other-third-country (Another third country (no adequacy decision)) |
answers.usControl | Is the provider US-owned, or does it have a US parent or subsidiaries that could be subject to compelled disclosure under FISA §702 or the CLOUD Act? Corporate control matters even where data is hosted in the EU, US-controlled entities can face extraterritorial disclosure obligations. | yes (Yes), no (No), unsure (Unsure) |
answers.hosting | Where is the data at rest stored? | eu-eea (EU / EEA only), us (United States), multi-region (Multi-region / global), unsure (Unsure) |
answers.subprocessors | How transparent are the sub-processors? | transparent (Transparent, a current list, contractually bound, with notice of changes), opaque (Opaque, unknown, or no meaningful list/commitments) |
answers.transferMechanism | What transfer mechanism is relied on for any third-country transfer? SCCs require a documented Transfer Impact Assessment and, where needed, supplementary measures; the DPF only covers US importers that are actively certified for the relevant data. | eu-only-or-adequacy (No third-country transfer, or transfer only to an adequacy country), sccs (EU Standard Contractual Clauses (with a TIA)), dpf (EU-US Data Privacy Framework (importer certified)), none-unclear (None in place / unclear) |
answers.encryptionAtRest | Encryption at rest and key custody? | customer-held (Customer-held keys / HYOK / BYOK (provider cannot decrypt unilaterally)), vendor-held (Encrypted, but the vendor holds the keys), none-unsure (No encryption at rest / unsure) |
answers.encryptionInTransit | Encryption in transit? | strong (Yes, strong, current TLS everywhere), none-unsure (No / unsure) |
answers.supportAccess | Support and engineering access to the data? | eu-only-controlled (EU-based support, with just-in-time and logged privileged access), global (Global support/engineering can access the data), unsure (Unsure) |
answers.aiLayer | Are third-party AI inference providers in the prompt or document path? An AI/processing layer that sends content to a third-party model provider is itself a transfer/sub-processor dimension. | none-or-eu (None, or EU-based providers with EU-only processing and no known third-country onward transfer), us-or-global (Yes, US or global third-party model providers), unsure (Unsure) |
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": "cloud_act_exposure",
"arguments": {
"answers": {
"euPersonalData": "yes",
"providerHq": "us",
"usControl": "yes",
"hosting": "eu-eea",
"subprocessors": "transparent",
"transferMechanism": "dpf",
"encryptionAtRest": "vendor-held",
"encryptionInTransit": "strong",
"supportAccess": "global",
"aiLayer": "none-or-eu"
}
}
}
}Response
The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.
{
"status": "result",
"verdict": {
"id": "tia-recommended",
"reading": "Reading from fixed rules, not a legal conclusion: Structured TIA needed: review the flagged dimensions",
"page_title": "Structured TIA needed: review the flagged dimensions",
"summary": "One or more transfer-exposure dimensions are elevated. This is a structured starting point, not a verdict: take the flagged dimensions below to your DPO/counsel, document a Transfer Impact Assessment, and decide on supplementary measures. Whether the transfer is lawful depends on facts beyond this questionnaire.",
"tone": "maybe"
},
"reasons": [
{
"code": "dim-jurisdiction",
"text": "Provider jurisdiction, headquartered in a third country without an adequacy decision."
},
{
"code": "dim-us-control",
"text": "US corporate control, potential FISA §702 / CLOUD Act compelled-disclosure exposure (applies even with EU hosting)."
},
{
"code": "dim-encryption-at-rest",
"text": "Encryption at rest, keys are vendor-held or absent, so the provider can decrypt unilaterally."
},
{
"code": "dim-support-access",
"text": "Support access, global support/engineering can reach the data, or controls are unclear."
},
{
"code": "structured-assessment-note",
"text": "This is a structured assessment to take to your DPO/counsel, not a compliance determination."
}
],
"obligations": [
"Re-examine the transfer mechanism: confirm SCCs are the current modules with a documented Transfer Impact Assessment, or that DPF certification actively covers the data in question.",
"Consider technical supplementary measures, strong encryption with customer-held keys (HYOK/BYOK) so the provider cannot decrypt unilaterally; data minimisation; pseudonymisation.",
"Constrain operational access, EU-based support, just-in-time and logged privileged access, documented access controls.",
"For the AI/processing layer, assess third-party model providers as sub-processors with your DPO; consider EU-based providers if minimisation or replacement is required.",
"These are categories to assess with counsel, not prescriptive vendor swaps; document the analysis as part of your accountability record."
],
"answered": 10,
"total": 10,
"basis": [
"GDPR Chapter V",
"CJEU Case C-311/18 (Schrems II)",
"EDPB Recommendations 01/2020",
"US CLOUD Act",
"FISA section 702"
],
"sources_checked_on": [
{
"source": "CJEU judgment of 16 July 2020, Case C-311/18 (Schrems II), EUR-Lex",
"checked_on": "2026-07-17"
},
{
"source": "EDPB Recommendations 01/2020 on supplementary measures, version 2.0, adopted 18 June 2021",
"checked_on": "2026-07-17"
},
{
"source": "US Department of Justice: CLOUD Act resources",
"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-cloud-act-exposure-analyzer",
"label": "Review your own documents against this framework with ISMS Copilot"
},
"tool_page": "https://www.ismscopilot.com/resources/cloud-act-exposure-analyzer"
}What the result rests on
Every result names its basis, as identifiers only (never standard text):
- GDPR Chapter V
- CJEU Case C-311/18 (Schrems II)
- EDPB Recommendations 01/2020
- US CLOUD Act
- FISA section 702
Sources the rules were checked against, with the date each was last checked:
- CJEU judgment of 16 July 2020, Case C-311/18 (Schrems II), EUR-Lex, checked 2026-07-17
- EDPB Recommendations 01/2020 on supplementary measures, version 2.0, adopted 18 June 2021, checked 2026-07-17
- US Department of Justice: CLOUD Act resources, 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.