fr.hermetics/rgpd

Est-ce que fr.hermetics/rgpd est sûr ?

Au dernier audit MCP Hub, le serveur MCP « fr.hermetics/rgpd » 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 8 outils

• gdpr_obligations≈ 810 tokens

  Lists the GDPR obligations of a company established in an EU or EEA country from a few facts (size, website and cookies, e-mail marketing, sensitive data, video surveillance, AI...). Deterministic rules: each obligation comes with its legal basis and a suggested search_law query for the official text. A fact left out is treated as unknown, except processors, which are assumed.

  Paramètres, retour & exemple (16)

  Paramètres

  • ai · boolean · optionnel
    True if it develops or uses AI systems that interact with or make decisions about people.
  • cctv · boolean · optionnel
    True if it uses video surveillance (CCTV).
  • country · string · requis · AT | BE | BG | HR | CY | CZ | DK | EE
    Country where the company is established (ISO code of an EU or EEA country, e.g. FR, DE, ES, IT).
  • website · boolean · optionnel
    True if the company has a website or app.
  • employees · integer · optionnel
    Number of employees (0 if none).
  • processors · boolean · optionnel
    True if providers process personal data on its behalf (hosting, SaaS, payroll, CRM). Assumed true if omitted.
  • large_scale · boolean · optionnel
    True if the processing concerns a large number of people (large scale).
  • public_sector · boolean · optionnel
    True if the organisation is a public authority or public body.
  • email_marketing · boolean · optionnel
    True if the company sends marketing e-mails or SMS to individuals.
  • vulnerable_people · boolean · optionnel
    True if it processes data of vulnerable people (children, patients, elderly people).
  • automated_decisions · boolean · optionnel
    True if it takes automated decisions with legal or similarly significant effects on people.
  • evaluation_or_scoring · boolean · optionnel
    True if it evaluates or scores people (credit scoring, profiling, performance rating).
  • non_essential_cookies · boolean · optionnel
    True if the website or app uses non-essential cookies or trackers (analytics, advertising, social media pixels).
  • special_category_data · boolean · optionnel
    True if it processes special category data (health, biometrics, genetic data, religion, union membership, sex life or orientation, ethnic origin, political opinions).
  • systematic_monitoring · boolean · optionnel
    True if it systematically monitors people (online behaviour tracking, geolocation, profiling for advertising, CCTV of public areas).
  • transfers_outside_eea · boolean · optionnel
    True if personal data is sent to providers or entities outside the EEA (e.g. US SaaS).

  Exemple d'appel

  {"name": "gdpr_obligations", "arguments": {"country": "AT"}}

  Exemple de retour

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

• list_processing_records≈ 212 tokens

  Lists the records of processing activities (GDPR art. 30(1)) saved in the Hermetics account linked to the connection, in their latest version, with their full content. For an account of a Hermetics client organization, lists the organization's whole register on the Hermetics platform, whatever the origin of each record, with its status. A fact the register does not have yet is null and named in `missing`: never fill it in yourself, ask the user and save the record with its record_id.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_processing_records", "arguments": {}}

  Exemple de retour

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

• pending_reviews≈ 146 tokens

  Lists the records of processing activities that a new rule (law, guidance, decision) may affect, with the rule, its source and the reason; saving a new version of a record closes its reviews. Reviews are part of the paid plans.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "pending_reviews", "arguments": {}}

  Exemple de retour

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

• prepare_analysis≈ 578 tokens

  Prepares, in the Hermetics space of the organization, the analysis of a record of the register with the same engines as the Hermetics platform: legal basis, DPIA, legitimate interests assessment, transfer impact assessment, information notice (art. 13 and 14), the privacy policy of the whole register, or the art. 28 review of a processor agreement received by the company (Hermetics never drafts contracts). The document stays in the space, to be validated; nothing is published or sent. Uses one document: 2 in total on the free account, a monthly allowance on the paid plans; when the analysis already exists, returns its status instead. Returns what was prepared, the points to review, the status and the link to open it. Prepared from the facts given; the decision is the user's, or the designated DPO validates it when the organization has one.

  Paramètres, retour & exemple (5)

  Paramètres

  • type · string · requis · legal_basis | dpia | lia | tia | information_notice | privacy_policy | processor_agreement_review
    legal_basis (art. 6), dpia (art. 35), lia (legitimate interests assessment), tia (transfer impact assessment, art. 44 to 49), information_notice (art. 13 and 14), privacy_policy (the whole register), processor_agreement_review (art. 28 review of a processor agreement received by the company).
  • notes · string · optionnel
    Facts or context from the user for the preparation; no personal data needed.
  • record_id · string · optionnel
    Code of the record in the register (e.g. AT-001); required for every type except privacy_policy.
  • agreement_text · string · optionnel
    Full text of the processor agreement received by the company (processor_agreement_review only).
  • processor_name · string · optionnel
    Name of the processor whose agreement is reviewed (processor_agreement_review only).

  Exemple d'appel

  {"name": "prepare_analysis", "arguments": {"type": "legal_basis"}}

  Exemple de retour

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

• record_request≈ 448 tokens

  Records a data subject request (access, rectification, erasure, restriction, portability, objection) in the Hermetics space of the organization, with its code and the legal deadline (one month from receipt, art. 12(3), extendable). Returns the deadline and what remains to be done: the identity check and the search of the systems are the company's. Nothing is sent to the requester. The free account tracks 10 requests a year; the paid plans have no limit. Prepared from the facts given; the decision is the user's, or the designated DPO validates it when the organization has one.

  Paramètres, retour & exemple (5)

  Paramètres

  • notes · string · optionnel
    Other context for the handling of the request.
  • right · string · requis · access | rectification | erasure | restriction | portability | objection
    The right exercised (GDPR art. 15 to 21).
  • channel · string · optionnel
    How the request arrived (e-mail, letter, phone, in person...).
  • received_on · string · requis
    Date the company received the request (YYYY-MM-DD): the one-month period runs from it.
  • requester_description · string · requis
    Who made the request and what was asked (e.g. "a former customer asking for a copy of their order history"); no sensitive data beyond what the request needs.

  Exemple d'appel

  {"name": "record_request", "arguments": {"right": "access", "received_on": "texte", "requester_description": "texte"}}

  Exemple de retour

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

• report_breach≈ 445 tokens

  Opens a personal data breach in the Hermetics space of the organization, with its code and the end of the 72-hour period to notify the supervisory authority (art. 33(1)), counted from when the company became aware of it. Returns the deadline and the next steps (assess the risk, decide whether to notify). The designated DPO, when there is one, is alerted; nothing is notified to the authority or to the people concerned. The free account tracks 10 breaches a year; the paid plans have no limit. Prepared from the facts given; the decision is the user's, or the designated DPO validates it when the organization has one.

  Paramètres, retour & exemple (5)

  Paramètres

  • ongoing · boolean · optionnel
    True if the breach is still ongoing.
  • description · string · requis
    What happened, the systems involved and the measures already taken; no personal data needed.
  • discovered_at · string · requis
    When the company became aware of the breach (ISO 8601 date and time with time zone): the 72-hour period runs from it.
  • data_categories · array · optionnel
    Categories of personal data concerned, e.g. "identity", "bank details".
  • people_count_estimate · integer · optionnel
    Approximate number of people concerned.

  Exemple d'appel

  {"name": "report_breach", "arguments": {"description": "texte", "discovered_at": "texte"}}

  Exemple de retour

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

• save_processing_record≈ 1044 tokens

  Saves one entry of the record of processing activities (GDPR art. 30(1)) in the Hermetics account linked to the connection: new records get a code and every change is kept as a new version, in the account's own register on the Hermetics platform (the free account has no DPO: the user checks the records). When the account belongs to a Hermetics client organization, records go to that organization's register on the Hermetics platform (codes AT-001...), pending its DPO's review; a change to a record the DPO has validated is sent to the DPO as a proposal. Returns the code, the version and the points a DPO would review in the entry; when an existing record is updated, also what changed from the previous version and what the change requires (information notice, proof of consent, processor contract, transfer safeguard, DPIA review). The free account stores 35 records; the paid plans have no record limit.

  Paramètres, retour & exemple (14)

  Paramètres

  • name · string · requis
    Short name of the processing activity (e.g. "Payroll", "Newsletter").
  • purpose · string · requis
    Purpose of the processing (art. 30(1)(b)).
  • record_id · string · optionnel
    Code of an existing record (e.g. RT-001, or AT-001 in an organization register) to save a new version of it; omit to create a new record.
  • retention · string · requis
    Retention period or the criteria used to determine it (art. 30(1)(f)).
  • processors · array · optionnel
    Processors acting on behalf of the company (art. 28).
  • recipients · array · requis
    Categories of recipients, internal and external (art. 30(1)(d)).
  • legal_basis · string · requis · consent | contract | legal_obligation | vital_interests | public_task | legitimate_interests
    Legal basis under art. 6(1).
  • data_subjects · array · requis
    Categories of data subjects (art. 30(1)(c)), e.g. "employees", "customers".
  • art9_exception · string · optionnel
    The art. 9(2) exception relied on, if special category data are processed.
  • data_categories · array · requis
    Categories of personal data (art. 30(1)(c)), e.g. "identity", "bank details".
  • security_measures · array · optionnel
    General description of technical and organisational security measures (art. 30(1)(g)).
  • legal_basis_details · string · optionnel
    Details of the legal basis: the legal obligation, the contract, or the legitimate interest pursued.
  • special_category_data · boolean · optionnel
    True if special category data (art. 9) are processed.
  • transfers_outside_eea · object · optionnel
    Transfers to third countries (art. 30(1)(e)); omit if none.

  Exemple d'appel

  {"name": "save_processing_record", "arguments": {"name": "texte", "purpose": "texte", "retention": "texte", "recipients": [], "legal_basis": "consent", "data_subjects": []}}

  Exemple de retour

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

• search_law≈ 312 tokens

  Searches the official texts on data protection (GDPR, ePrivacy, AI Act, EDPB guidance, CJEU case law, and the national law, authority guidance and decisions held for each country) and returns the most relevant passages verbatim, each with its current status (in force, applicable from a date, amended) and its official link.

  Paramètres, retour & exemple (2)

  Paramètres

  • country · string · optionnel · AT | BE | BG | HR | CY | CZ | DK | EE
    ISO code of an EU or EEA country (e.g. FR, DE, ES) to add its national law and authority guidance to the EU texts; omit for EU texts only.
  • question · string · requis
    The legal question, in any language (French gives the best results today). Names and personal data are not needed.

  Exemple d'appel

  {"name": "search_law", "arguments": {"question": "texte"}}

  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://hermetics.fr/api/mcp