court_opinion_search
Full-text search of court opinions. Returns opinion text snippets, authors, and citations.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/court-opinion-search.md
What court_opinion_search does on Livedatalink
AI agents call court_opinion_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 ID filter. |
limit | number | — | Max results (1-50, default 10). |
query | string | Yes | Search text required. |
Parameters from the server's own tool schema.
Why court_opinion_search is rated Low
This tool performs a search and retrieval operation on public court opinion data. It returns existing data (opinion text, author information, citations) without modifying, deleting, or executing anything. The operation is read-only with no side effects. The data returned is publicly available court information, making it low risk even if accessed inappropriately.
From the tool's definition Full-text search of court opinions. Returns opinion text snippets, authors, and citations.
Attacks that exploit this kind of access
The rule that runs court_opinion_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_opinion_search, this is the rule to start with:
court_opinion_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_opinion_search call is checked against it from then on.
Questions about court_opinion_search
Full-text search of court opinions. Returns opinion text snippets, authors, and citations. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
court_opinion_search accepts 3 parameters: court, limit, query. Required: query. 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_opinion_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_opinion_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_opinion_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_opinion_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_opinion_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