Recherche dans les textes légaux historiques avec validation MCP. Il faut impérativement citer le contenu trouvé avec le lien officiel fournis par legifrance. Args: search: Mots-clés de recherche ou numéro d'article text_id: Le numéro du texte (format AAAA-NUMERO) (optionnel) champ: Champ de rech...
Part of the Openlegi server.
Free to start. No card required.
AI agents call rechercher_dans_texte_legal to retrieve information from Openlegi without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though rechercher_dans_texte_legal only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"rechercher_dans_texte_legal": {}
}
}See the full Openlegi policy for all 7 tools.
These attack patterns abuse exactly the kind of access rechercher_dans_texte_legal gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Recherche dans les textes légaux historiques avec validation MCP. Il faut impérativement citer le contenu trouvé avec le lien officiel fournis par legifrance. Args: search: Mots-clés de recherche ou numéro d'article text_id: Le numéro du texte (format AAAA-NUMERO) (optionnel) champ: Champ de recherche ("ALL", "TITLE", "TABLE", "NUM_ARTICLE", "ARTICLE") sort: Tri des résultats ("PERTINENCE" (défaut), "PUBLICATION_DATE_DESC" (antéchronologique) , "PUBLICATION_DATE_ASC" (chronologique)) type_recherche: Type de recherche ("TOUS_LES_MOTS_DANS_UN_CHAMP" (defaut), "EXACTE", "UN_DES_MOT") max_results: Nombre de résultats (defaut: 10, maximum: 100) Returns: Résultats formatés avec messages d'erreur contextuels Exemples: - Pour l'article 7 de la loi 78-17: rechercher_dans_texte_legal("7", text_id="78-17", champ="NUM_ARTICLE") - Signature électronique: rechercher_dans_texte_legal("signature électronique validité conditions"). It is categorised as a Read tool in the Openlegi MCP Server, which means it retrieves data without modifying state.
Register the Openlegi MCP server in PolicyLayer and add a rule for rechercher_dans_texte_legal: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Openlegi. Nothing to install.
rechercher_dans_texte_legal is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rechercher_dans_texte_legal rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for rechercher_dans_texte_legal. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
rechercher_dans_texte_legal is provided by the Openlegi MCP server (rdassignies/openlegi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Openlegi tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.