Search court opinions by keyword. Returns case names, citations, courts, and dates. Args: query: Legal search terms (e.g., "ERISA arbitrary capricious standard of review insurance denial") court: Court filter — "scotus", "all_appeals", "ca9", "ca5", "ca3", "ca7", or "" for all filed_after: Date f...
Risk signalsAccepts freeform code/query input (query)
Part of the Case Law Search server.
Free to start. No card required.
AI agents call search_case_law to retrieve information from Case Law Search 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 search_case_law 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.
{
"version": "1",
"default": "deny",
"tools": {
"search_case_law": {}
}
}See the full Case Law Search policy for all 4 tools.
These attack patterns abuse exactly the kind of access search_case_law gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search court opinions by keyword. Returns case names, citations, courts, and dates. Args: query: Legal search terms (e.g., "ERISA arbitrary capricious standard of review insurance denial") court: Court filter — "scotus", "all_appeals", "ca9", "ca5", "ca3", "ca7", or "" for all filed_after: Date filter YYYY-MM-DD (e.g., "2020-01-01") filed_before: Date filter YYYY-MM-DD cited_gt: Minimum citation count (use to find influential cases) max_results: Number of results (default 10, max 20). It is categorised as a Read tool in the Case Law Search MCP Server, which means it retrieves data without modifying state.
Register the Case Law Search MCP server in PolicyLayer and add a rule for search_case_law: 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 Case Law Search. Nothing to install.
search_case_law 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_case_law 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_case_law. 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_case_law is provided by the Case Law Search MCP server (alexandria-shai-eden/caselaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Case Law Search 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.