caselaw_search
Search US court opinions (Caselaw Access Project, public domain) by case name / keyword, court, jurisdiction, and decision-date range. Returns matching case metadata with CAP ids and citations. Use caselaw_opinion_text with a returned id to read the full opinion. Note: v1 index covers the U.S. Re...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/caselaw-search.md
What caselaw_search does on Livedatalink
AI agents call caselaw_search to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
court | string | — | Optional court-name fragment, e.g. 'Supreme Court'. |
limit | number | — | Maximum rows to return (default 25, max 100). |
query | string | — | Case name or keyword, e.g. 'Brown Board Education', 'Miranda'. |
end_date | string | — | Optional ISO date upper bound (YYYY-MM-DD). |
start_date | string | — | Optional ISO date lower bound (YYYY-MM-DD). |
jurisdiction | string | — | Optional jurisdiction fragment, e.g. 'United States'. |
Parameters from the server's own tool schema.
Why caselaw_search is rated Low
Even though caselaw_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs caselaw_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For caselaw_search, this is the rule to start with:
caselaw_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every caselaw_search call is checked against it from then on.
Questions about caselaw_search
Search US court opinions (Caselaw Access Project, public domain) by case name / keyword, court, jurisdiction, and decision-date range. Returns matching case metadata with CAP ids and citations. Use caselaw_opinion_text with a returned id to read the full opinion. Note: v1 index covers the U.S. Reports reporter (official US Supreme Court reporter). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
caselaw_search accepts 6 parameters: court, limit, query, end_date, start_date, jurisdiction. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for caselaw_search: 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 Livedatalink. Nothing to install.
caselaw_search 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 caselaw_search 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 caselaw_search. 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.
caselaw_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue