Low Risk

recherche_journal_officiel

Recherche dans le Journal Officiel français avec validation MCP Args: search: Mots-clés à rechercher (ex: "nomination culture") champ: Champ de recherche ("ALL", "TITLE", "TABLE", "NOR", "NUM", "NUM_ARTICLE", "ARTICLE", "VISA", "NOTICE", "VISA_NOTICE", "TRAVAUX_PREP", "SIGNATURE", "NOTA") type_re...

Part of the Openlegi server.

recherche_journal_officiel is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OPENLEGI →

Free to start. No card required.

AI agents call recherche_journal_officiel 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 recherche_journal_officiel 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "recherche_journal_officiel": {}
  }
}

See the full Openlegi policy for all 7 tools.

Get this rule live on your own Openlegi server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPENLEGI →

These attack patterns abuse exactly the kind of access recherche_journal_officiel gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so recherche_journal_officiel only ever does what you allow.

SECURE OPENLEGI →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the recherche_journal_officiel tool do? +

Recherche dans le Journal Officiel français avec validation MCP Args: search: Mots-clés à rechercher (ex: "nomination culture") champ: Champ de recherche ("ALL", "TITLE", "TABLE", "NOR", "NUM", "NUM_ARTICLE", "ARTICLE", "VISA", "NOTICE", "VISA_NOTICE", "TRAVAUX_PREP", "SIGNATURE", "NOTA") type_recherche: Type de recherche ("TOUS_LES_MOTS_DANS_UN_CHAMP" (defaut), "EXACT", "UN_DES_MOT") sort: Tri des résultats, par défaut "PERTINENCE" ("PERTINENCE", "SIGNATURE_DATE_DESC", "SIGNATURE_DATE_ASC", "PUBLI_DATE_DESC", "PUBLI_DATE_ASC") date_publication: Date de publication sous forme de liste [date_debut, date_fin] au format YYYY-MM-DD ministeres: Liste des ministères (optionnel) emetteurs: Liste des émetteurs/autorités (optionnel) - outil "lister_emetteurs_jorf" pour la liste complète text_types: Types de textes (LOI, DECRET, ARRETE, etc.) - outil "lister_natures_textes_jorf" pour la liste des textes publiés au JORF max_results: Nombre maximum de résultats (défaut: 5, maximum: 100) Returns: Résultats formatés avec messages d'erreur contextuels Exemples: - Recherche simple: recherche_journal_officiel("nomination cinéma") - Avec filtres: recherche_journal_officiel("nomination", ministeres=["MINISTERE_CULTURE"], text_types=["ARRETE"]) - Pour rechercher avec tri du plus récent au plus ancien (sort="SIGNATURE_DATE_DESC) Notes: Utilisez 'lister_emetteurs_jorf' pour voir tous les émetteurs disponibles Utilisez 'lister_natures_textes_jorf' pour voir la liste des types de textes publiés au JO. It is categorised as a Read tool in the Openlegi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on recherche_journal_officiel? +

Register the Openlegi MCP server in PolicyLayer and add a rule for recherche_journal_officiel: 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.

What risk level is recherche_journal_officiel? +

recherche_journal_officiel is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit recherche_journal_officiel? +

Yes. Add a rate_limit block to the recherche_journal_officiel 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.

How do I block recherche_journal_officiel completely? +

Set action: deny in the PolicyLayer policy for recherche_journal_officiel. 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.

What MCP server provides recherche_journal_officiel? +

recherche_journal_officiel 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.

Enforce policy on every Openlegi tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.