Low Risk

get_decision_judiciaire

Extraction du texte intégral d'une décision judiciaire via l'API restreinte PISTE (authentification OAuth2 requise). À substituer systématiquement par get_decision_judiciaire_libre lorsque la décision figure dans les archives ouvertes de la DILA. Outil formellement inopérant pour les décisions re...

Part of the Justicelibre server.

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

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

Extraction du texte intégral d'une décision judiciaire via l'API restreinte PISTE (authentification OAuth2 requise). À substituer systématiquement par get_decision_judiciaire_libre lorsque la décision figure dans les archives ouvertes de la DILA. Outil formellement inopérant pour les décisions relevant de l'ordre administratif (formats DCE_*, DTA_*, DCAA_*, /Ariane_Web/...). Args: decision_id: identifiant Judilibre de la décision session_token: jeton justicelibre temporaire (recommandé) client_id: Client ID PISTE (alternative) client_secret: Client Secret PISTE (alternative). 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 get_decision_judiciaire? +

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

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

Can I rate-limit get_decision_judiciaire? +

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

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

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