search_local
AI agents call search_local to retrieve information from JurisCassation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to search indexed Court of Cassation decisions locally without retrieving external content or modifying data. This is a Read operation with low severity due to limited blast radius—even if an AI agent misuses it, the worst outcome is retrieving irrelevant or sensitive court documents, not deletion or execution of arbitrary code.
From the tool's definition Tool name 'search_local' with sibling tools including 'search_decisions', 'list_chambers', and 'get_stats' indicates a read-only query pattern. Server description emphasizes 'search tools' and 'queries against the official portal'.
Attacks that exploit this kind of access
search_local. It is categorised as a Read tool in the JurisCassation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JurisCassation MCP Server MCP server in PolicyLayer and add a rule for search_local: 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 JurisCassation MCP Server. Nothing to install.
search_local 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_local 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_local. 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_local is provided by the JurisCassation MCP Server MCP server (slapash/juriscassation-api). 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 →