judilibre_decision
AI agents call judilibre_decision 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.
Based on the server's stated purpose of covering French law via open judicial data and the naming pattern of sibling tools, this tool almost certainly retrieves or queries judicial decision data without modifying or deleting it. The absence of a description lowers confidence slightly, but the context strongly suggests a read-only data access tool typical of legal document APIs.
From the tool's definition Tool is part of JUDILIBRE API wrapping suite that provides access to 'open data judicial decisions' from French courts. The name 'judilibre_decision' and context of sibling tools (search, stats, export, scan) indicate data retrieval functionality.
Attacks that exploit this kind of access
judilibre_decision. 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_decision: 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_decision 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_decision 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_decision. 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_decision 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 →