Décisions admin récentes triées chronologiquement (API live). Priorité au récent : tri par date de lecture décroissante, pas par pertinence. Utile pour "actualité d'une juridiction" mais PAS pour trouver la jurisprudence pertinente sur un sujet — pour cela, utiliser search_admin (bulk JADE avec B...
Risk signalsAccepts freeform code/query input (query) · Admin/system-level operation
Part of the Justicelibre server.
Free to start. No card required.
AI agents call search_admin_recent 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_recent 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": {
"search_admin_recent": {}
}
}See the full Justicelibre policy for all 30 tools.
These attack patterns abuse exactly the kind of access search_admin_recent 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.
Décisions admin récentes triées chronologiquement (API live). Priorité au récent : tri par date de lecture décroissante, pas par pertinence. Utile pour "actualité d'une juridiction" mais PAS pour trouver la jurisprudence pertinente sur un sujet — pour cela, utiliser search_admin (bulk JADE avec BM25 ranking). Périmètre : CE + 9 CAA + 40 TA (incluant l'outre-mer), depuis ~2022. Les identifiants générés (formats DCE_*, DTA_*, DCAA_*) sont nativement compatibles avec l'outil get_decision_text. Args: query: mots-clés de recherche juridiction: code de la juridiction. Exemples : - "CE" — Conseil d'État - "CE-CAA" — Conseil d'État + cours administratives d'appel - "TA69" — Tribunal administratif de Lyon - "TA75" — Tribunal administratif de Paris - "CAA69" — Cour administrative d'appel de Lyon Les codes "TA" ou "CAA" isolés retournent un résultat vide — un code spécifique est requis. Consulter list_juridictions pour la nomenclature complète. 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.
Register the Justicelibre MCP server in PolicyLayer and add a rule for search_admin_recent: 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.
search_admin_recent 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 search_admin_recent 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 search_admin_recent. 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.
search_admin_recent 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.
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.