judilibre_scan
AI agents call judilibre_scan to retrieve information from Mpc Judilibre without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is part of a JUDILIBRE API wrapper server exposing French court decisions. The name 'scan' implies data retrieval/search rather than modification, creation, deletion, or execution of code. The absence of a description lowers confidence slightly, but context from sibling tools (historique, rechercher, stats, taxonomie, export) all suggest read-only query operations.
From the tool's definition Tool name 'judilibre_scan' suggests querying/scanning judicial decisions from the JUDILIBRE API (open data from French courts).
Attacks that exploit this kind of access
judilibre_scan. It is categorised as a Read tool in the Mpc Judilibre MCP Server, which means it retrieves data without modifying state.
Register the Mpc Judilibre MCP server in PolicyLayer and add a rule for judilibre_scan: 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 Mpc Judilibre. Nothing to install.
judilibre_scan 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 judilibre_scan 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 judilibre_scan. 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.
judilibre_scan is provided by the Mpc Judilibre MCP server (ktulu-analog/mcp-judilibre). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →