Low Risk

search_judiciaire_libre

Recherche plein texte dans la jurisprudence judiciaire, exécutée localement et affranchie de toute obligation d'authentification gouvernementale. Exploite l'index FTS5 des archives publiques DILA (~620 000 décisions : Cour de cassation, 36 cours d'appel, Conseil constitutionnel). Scoring BM25 dis...

Risk signalsAccepts freeform code/query input (query)

Part of the Justicelibre server.

search_judiciaire_libre 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 JUSTICELIBRE →

Free to start. No card required.

AI agents call search_judiciaire_libre to retrieve information from Justicelibre 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 search_judiciaire_libre 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": {
    "search_judiciaire_libre": {}
  }
}

See the full Justicelibre policy for all 30 tools.

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

ENFORCE ON MY JUSTICELIBRE →

View all 30 tools →

These attack patterns abuse exactly the kind of access search_judiciaire_libre 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 search_judiciaire_libre only ever does what you allow.

SECURE JUSTICELIBRE →

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

What does the search_judiciaire_libre tool do? +

Recherche plein texte dans la jurisprudence judiciaire, exécutée localement et affranchie de toute obligation d'authentification gouvernementale. Exploite l'index FTS5 des archives publiques DILA (~620 000 décisions : Cour de cassation, 36 cours d'appel, Conseil constitutionnel). Scoring BM25 disponible mais tri appliqué par ordre chronologique décroissant. Couverture connue : la base contient un sous-ensemble des arrêts publiés par les CA en open data DILA (~73 000 arrêts CA, principalement depuis 2007). Tous les arrêts ne sont PAS dans la base ; un faux négatif n'implique donc pas que l'arrêt n'existe pas. En cas de bredouille, suggérer à l'utilisateur de chercher sur Légifrance ou via PISTE (search_judiciaire). Recherche par numéro de RG : pour les arrêts CA, utiliser le param numero_rg (lookup direct, normalise les variantes 21/05835, 21-05835, 2105835). Pour les pourvois Cass, utiliser query avec le numéro (ex: query="21-12.345"). ⚠️ Les résultats ne contiennent qu'un SNIPPET tronqué (snippet), pas le texte intégral. Pour lire une décision en entier, appeler get_decision_judiciaire_libre(id) avec l'id retourné (format JURITEXT* Cass / cours d'appel, CONSTEXT* Conseil constitutionnel). Ne pas se fier au snippet seul pour conclure sur le contenu. Args: query: mots-clés (ex : "licenciement abusif"). FTS5 supporte "phrase exacte", mot1 AND mot2, mot* (préfixe). Optionnel si numero_rg est fourni. juridiction: filtre optionnel : "cassation" / "appel" / "constit". numero_rg: numéro RG d'un arrêt CA (ex: "21/05835"). Lookup direct qui matche toutes les variantes typographiques. date_min: date min ISO (YYYY-MM-DD), optionnel date_max: date max ISO (YYYY-MM-DD), optionnel limit: nombre maximum de résultats (défaut 20). It is categorised as a Read tool in the Justicelibre MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_judiciaire_libre? +

Register the Justicelibre MCP server in PolicyLayer and add a rule for search_judiciaire_libre: 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 Justicelibre. Nothing to install.

What risk level is search_judiciaire_libre? +

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

Can I rate-limit search_judiciaire_libre? +

Yes. Add a rate_limit block to the search_judiciaire_libre 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 search_judiciaire_libre completely? +

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

search_judiciaire_libre is provided by the Justicelibre MCP server (https://justicelibre.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Justicelibre tool call.

Deterministic rules across all 30 Justicelibre 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.