Low Risk

search_conseil_etat

Recherche sémantique ciblée sur la jurisprudence du Conseil d'État (base ArianeWeb, ~270 000 décisions). Moteur exclusif disposant d'un véritable algorithme de pertinence (Sinequa) avec extraction de contexte. À privilégier systématiquement pour le droit public. EXTRACTION DU TEXTE : les ids reto...

Risk signalsAccepts freeform code/query input (query)

Part of the Justicelibre server.

search_conseil_etat 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_conseil_etat 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_conseil_etat 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_conseil_etat": {}
  }
}

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_conseil_etat 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_conseil_etat 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_conseil_etat tool do? +

Recherche sémantique ciblée sur la jurisprudence du Conseil d'État (base ArianeWeb, ~270 000 décisions). Moteur exclusif disposant d'un véritable algorithme de pertinence (Sinequa) avec extraction de contexte. À privilégier systématiquement pour le droit public. EXTRACTION DU TEXTE : les ids retournés (/Ariane_Web/AW_DCE/|XXXXXX) sont DÉSORMAIS exploitables directement par get_decision_text(id) (récupération live via le plugin Sinequa). ⚠️ COUVERTURE : cet index ArianeWeb (Sinequa) couvre MAL les arrêts anciens/fondateurs (avant ~1990). Si une recherche ici renvoie 0, NE PAS conclure que l'arrêt est absent de JusticeLibre : le bulk JADE (search_admin) couvre le CE depuis 1873 (Trompier-Gravier 1944, PGD, etc. inclus). Et si tu connais déjà l'id Légifrance CETATEXT… d'un arrêt, get_decision_text("CETATEXT…") le sort directement du bulk. Consigne de recherche : limiter les requêtes à 2-5 mots-clés distinctifs ; les requêtes en phrase complète retournent généralement zéro résultat. Args: query: mots-clés de recherche (ex : "référé liberté", "QPC 145") limit: nombre maximum de résultats (défaut 20) offset: décalage pour paginer (défaut 0). Réitérer avec offset=20, offset=40, etc. pour obtenir les pages suivantes.. 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_conseil_etat? +

Register the Justicelibre MCP server in PolicyLayer and add a rule for search_conseil_etat: 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_conseil_etat? +

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

Can I rate-limit search_conseil_etat? +

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

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

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