judilibre_historique
AI agents call judilibre_historique 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.
Despite the empty description reducing confidence slightly, the naming pattern and server context strongly indicate this is a Read operation retrieving historical judicial decisions or metadata from the PISTE platform. No modification, execution, or destructive capability is suggested. Severity is low because the data is explicitly open/public and read-only access poses minimal risk.
From the tool's definition Tool name 'judilibre_historique' suggests retrieval of historical data from the JUDILIBRE API. Sister tools on the server (judilibre_decision, judilibre_rechercher, judilibre_stats, judilibre_taxonomie) are all query/retrieval operations.
Attacks that exploit this kind of access
judilibre_historique. 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_historique: 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_historique 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_historique 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_historique. 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_historique 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 →