Double AIgents DSAR service

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

GDPR DSAR deadlines, breach triage, AI tool checks, HR retention and letters (UK/EU/CH)

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Double AIgents DSAR service": {
      "url": "https://www.doubleaigents.com/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (10)

• dsar_deadline read-only

  Calculate the statutory deadline for answering a data subject access request in the UK, the EU/EEA or Switzerland, with the rule that applies and the extension position. General information, not legal advice.

  Parameters:

  • jurisdiction (required) — string — UK, EU (EU/EEA GDPR) or CH (Switzerland).
  • received_date (required) — string — ISO date the clock starts. For the UK, the later of receipt and receipt of any requested ID or fee.
  • extended — boolean — Also calculate the extended deadline where an extension is available.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• dsar_quote read-only

  Fixed price from Double AIgents for preparing a DSAR response, by pack size in pages after de-duplication. Also gives the retainer price (15% off). Excludes VAT.

  Parameters:

  • pages (required) — integer — Number of pages after de-duplication.
  • currency — string — GBP (UK), EUR (EU/EEA) or CHF (Switzerland).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• dsar_service_info read-only

  What the Double AIgents DSAR service covers: scoping, collection guidance, de-duplication, redaction, exemption recommendations, two independent reviews, secure delivery, data handling, jurisdictions and partner arrangements.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• dsar_request_scoping read-only

  Explains how to start free scoping and returns a prefilled email (mailto URL) to [email protected]. Sends nothing and stores nothing. Do not pass the requester's personal data or the request letter.

  Parameters:

  • organisation (required) — string — The controller organisation that received the request.
  • contact_name (required) — string — Name of the person at the organisation handling the request (not the requester).
  • contact_email (required) — string — Email of that person.
  • jurisdiction (required) — string
  • date_received (required) — string — ISO date the request was received.
  • approx_volume — string — Optional rough volume, for example "two mailboxes, about 3 years".

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• breach_clock read-only

  When a personal data breach must be notified to the regulator: 72 hours from awareness in the UK and EU/EEA (Art. 33), "as soon as possible" in Switzerland (revised FADP Art. 24). Gives the deadline, the rule, the processor and individual-notification position, and the facts the regulator will ask for. The controller decides whether to notify. General information, not legal advice.

  Parameters:

  • jurisdiction (required) — string — UK, EU (EU/EEA GDPR) or CH (Switzerland).
  • aware_at (required) — string — ISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• dsar_letter_template read-only

  Plain-text letter template, in British English with [placeholders], for an acknowledgement, an extension of time or a request for clarification of a data subject access request, under UK, EU/EEA or Swiss law. Fills in the dates if received_date is given. General information, not legal advice.

  Parameters:

  • kind (required) — string
  • jurisdiction (required) — string — UK, EU (EU/EEA GDPR) or CH (Switzerland).
  • due_date — string — Optional ISO due date, used in place of the calculated one.
  • received_date — string — Optional ISO date the clock started. For the UK, the later of receipt and receipt of any requested ID or fee.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• breach_triage read-only

  A likely-reportability view on a personal data breach (UK, EU/EEA, Switzerland), following the ICO guide "Personal data breaches: a guide" and EDPB Guidelines 9/2022: whether notifying the regulator and telling the people affected is likely or unlikely to be required, the factors behind that view, and the notification deadline. The controller decides. General information, not legal advice. Do not pass names or other personal data.

  Parameters:

  • jurisdiction (required) — string — UK, EU (EU/EEA GDPR) or CH (Switzerland).
  • aware_at (required) — string — ISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00.
  • people_affected (required) — Approximate number of people affected, or "unknown".
  • special_category (required) — boolean — True if special category or criminal offence data is involved (health, biometric, criminal records, etc.).
  • recipient (required) — string — Who received or could access the data: a trusted internal person, a trusted external professional, unknown or the public, or a malicious actor.
  • recoverable (required) — string — Whether the data has been recovered or deletion confirmed, is likely to be, or not.
  • encrypted (required) — boolean — True if the data was strongly encrypted and the key was not compromised.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• ai_tool_check read-only

  Screens a planned use of an AI tool: whether a DPIA is likely to be required (Art. 35(3), the ICO high-risk list, the WP248 criteria; FADP Art. 22 for Switzerland), EU AI Act risk flags (Annex III high-risk areas, especially employment; Art. 5 prohibited practices such as emotion recognition at work; current application dates after the Digital Omnibus), and automated decision rules (GDPR Art. 22, UK GDPR Arts 22A to 22D). Findings with sources. The use_case text is not stored or returned. General information, not legal advice.

  Parameters:

  • use_case (required) — string — Short description of what the AI tool does. No personal data. Not stored.
  • processes_personal_data (required) — boolean
  • special_category (required) — boolean — Health, biometric, criminal offence data and the like.
  • employees_or_candidates (required) — boolean — True if it processes data about staff or job candidates.
  • automated_decisions_with_significant_effect (required) — boolean — True if it makes or drives decisions with legal or similarly significant effects without meaningful human involvement.
  • new_technology (required) — boolean — True if it is an innovative use or new technology for the organisation.
  • large_scale (required) — boolean
  • jurisdiction (required) — string — UK, EU (EU/EEA) or CH (Switzerland).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• hr_retention read-only

  Recommended retention period for a common UK HR record, whether it is statutory or only recommended, and the source (HMRC, Home Office, RIDDOR 2013, Working Time Regulations, Limitation Act 1980, ICO, DBS). UK only for now. General information, not legal advice.

  Parameters:

  • record_type (required) — string
  • jurisdiction — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• dsar_search_checklist read-only

  Where to search when answering a subject access request, especially from an employee: Microsoft 365 (Exchange and archives, shared mailboxes, Teams, OneDrive, SharePoint), other collaboration tools, HR, payroll, recruitment, CCTV, access logs, devices, line manager notes, paper files, occupational health and backups; search-term tips; and the search standard (UK GDPR Art. 15(1A) reasonable and proportionate searches). General information, not legal advice.

  Parameters:

  • organisation_type (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.