court_case_search
Search federal and state court opinions by keyword, court, judge, party name, or date range. Returns case summaries with citations.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/court-case-search.md
What court_case_search does on Livedatalink
AI agents call court_case_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 | — | Court ID, e.g. 'scotus', 'ca9', 'nysd'. |
judge | string | — | Judge name filter. |
limit | number | — | Max results (1-50, default 10). |
party | string | — | Party name filter. |
query | string | — | Free-text search query. |
date_filed_after | string | — | ISO date YYYY-MM-DD. |
date_filed_before | string | — | ISO date YYYY-MM-DD. |
Parameters from the server's own tool schema.
Why court_case_search is rated Low
This tool queries a public court records database and returns information. It has no side effects on the data, does not execute code or commands, and does not create, modify, or delete records. The search-and-return pattern is characteristic of Read category tools.
From the tool's definition Tool description states it 'Search[es]' court opinions and 'Returns case summaries with citations' — purely retrieval operations with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
The rule that runs court_case_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 court_case_search, this is the rule to start with:
court_case_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 court_case_search call is checked against it from then on.
Questions about court_case_search
Search federal and state court opinions by keyword, court, judge, party name, or date range. Returns case summaries with citations. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
court_case_search accepts 7 parameters: court, judge, limit, party, query, date_filed_after, date_filed_before. 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 court_case_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.
court_case_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 court_case_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 court_case_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.
court_case_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