Low Risk

search_admin

Recherche pondérée par pertinence BM25 sur la jurisprudence administrative complète (Conseil d'État + 9 CAA + 40 TA). Source : bulk JADE DILA (~550 k décisions full text). Contrairement aux outils search_admin_recent* qui trient par date, celui-ci classe par pertinence sémantique des mots-clés. I...

Risk signalsAccepts freeform code/query input (query) · Admin/system-level operation

Part of the Justicelibre server.

search_admin 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_admin 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_admin 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_admin": {}
  }
}

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

Recherche pondérée par pertinence BM25 sur la jurisprudence administrative complète (Conseil d'État + 9 CAA + 40 TA). Source : bulk JADE DILA (~550 k décisions full text). Contrairement aux outils search_admin_recent* qui trient par date, celui-ci classe par pertinence sémantique des mots-clés. Indispensable pour trouver LES bonnes décisions sur un sujet sans dépendre de l'ancienneté. ⚠️ Si tu cherches par numéro de requête (7 chiffres ex: 2200433), utilise plutôt get_admin_decision(numero, juridiction=...) qui fait un lookup SQL exact. La recherche FTS5 d'un numéro court ne le trouve que dans les décisions qui le citent dans leur texte (ex: décision de cassation), pas la décision identifiée par ce numéro. Args: query: mots-clés (opérateurs FTS5 : AND/OR/NOT, "phrase exacte", mot*) juridiction: filtre par fragment de nom de juridiction. Ex : "Lyon" → toutes les décisions Lyon (TA + CAA), "Tribunal Administratif de Lyon" → uniquement TA Lyon. Combiné en FTS5 AND avec la query principale. sort: "relevance" (défaut, BM25) ou "date_desc" / "date_asc" date_min: limite inférieure ISO YYYY-MM-DD (optionnel) date_max: limite supérieure ISO YYYY-MM-DD (optionnel) limit: nombre de résultats (défaut 20, max 50) offset: pagination Returns: {"total", "returned", "decisions": [...]} avec extracts BM25.. 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_admin? +

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

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

Can I rate-limit search_admin? +

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

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

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