Playbooks for source-led compliance work.
Choose a research path, then read the official source before you rely on a summary. Rekvira provides the text and pinpoints; your professional makes the conclusion.
8 paths ready to use
8 compliance workflows ship in the MCP library — each names the tools above in order.
- high-risk-triage — A product team describes an AI use case and you need Article 6, Annex III context, and deployer obligations before anyone claims compliance with
list_regulationsandsearch_regulation - deployer-obligations — You know the addressee role (deployer, provider) and need the heading index — not keyword search — before reading article text with
list_regulationsandlookup_obligations - dora-ict-third-party — Vendor or internal ICT service maps to DORA — contract clauses, register entries, and Article-level duties on ICT risk management with
list_regulationsandsearch_regulation - cross-reg-compliance-scan — The question spans AI rules, ICT/digital operational resilience, and/or personal-data law — search all loaded modules before reading pinpoints with
search_regulationsandread_unit - vendor-ai-questionnaire — A supplier questionnaire asks what the regulation requires — answer from held text with pinpoints, not from memory with
search_regulationandread_unit - cra-economic-operator-obligations — A product with digital elements maps to the Cyber Resilience Act — you know the economic-operator role and need the heading index before reading article text with
list_regulationsandlookup_obligations - gdpr-dpia-lookup — Privacy counsel needs Article 35 DPIA duties from held GDPR text with
list_regulationsandlookup_obligations - nis2-essential-entity — An essential or important entity needs NIS2 duties from held Directive text — heading index will be empty; read also_named then search, read, and verify with
list_regulationsandlookup_obligations
Connect Rekvira to use a playbook with your assistant.