com.doubleaigents.www/dsar

Est-ce que com.doubleaigents.www/dsar est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.doubleaigents.www/dsar » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 10 outils

• ai_tool_check≈ 491 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

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

  Exemple d'appel

  {"name": "ai_tool_check", "arguments": {"use_case": "texte", "large_scale": true, "jurisdiction": "UK", "new_technology": true, "special_category": true, "employees_or_candidates": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• breach_clock≈ 272 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "breach_clock", "arguments": {"aware_at": "texte", "jurisdiction": "UK"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• breach_triage≈ 535 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

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

  Exemple d'appel

  {"name": "breach_triage", "arguments": {"aware_at": "texte", "encrypted": true, "recipient": "trusted_internal", "recoverable": "confirmed_deleted", "jurisdiction": "UK", "people_affected": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dsar_deadline≈ 246 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "dsar_deadline", "arguments": {"jurisdiction": "UK", "received_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dsar_letter_template≈ 291 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "dsar_letter_template", "arguments": {"kind": "acknowledgement", "jurisdiction": "UK"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dsar_quote≈ 184 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "dsar_quote", "arguments": {"pages": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dsar_request_scoping≈ 329 tokens

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

  Paramètres, retour & exemple (6)

  Paramètres

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

  Exemple d'appel

  {"name": "dsar_request_scoping", "arguments": {"contact_name": "texte", "jurisdiction": "UK", "organisation": "texte", "contact_email": "texte", "date_received": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dsar_search_checklist≈ 224 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • organisation_type · string · requis · employer | law_firm | other

  Exemple d'appel

  {"name": "dsar_search_checklist", "arguments": {"organisation_type": "employer"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dsar_service_info≈ 136 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "dsar_service_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• hr_retention≈ 259 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • record_type · string · requis · payroll_paye | right_to_work | accident_book_riddor | unsuccessful_candidates | personnel_file_after_leaving | disciplinary_grievance | sickness_absence | maternity_smp
  • jurisdiction · string · optionnel · UK

  Exemple d'appel

  {"name": "hr_retention", "arguments": {"record_type": "payroll_paye"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.doubleaigents.com/api/mcp