legal.caselaw.search
Search US federal and state court opinions — filter by court (scotus, ca9, dcd...), date range, relevance. Largest free US case law archive. 7,000+ AI-related opinions (CourtListener / Free Law Project)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/legal.caselaw.search.md
What legal.caselaw.search does on Apibase
AI agents call legal.caselaw.search to retrieve information from Apibase 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 |
|---|---|---|---|
type | string | — | Search type: "o" (opinions, default) or "r" (RECAP dockets) |
court | string | — | Court filter (e.g. "scotus" for Supreme Court, "ca9" for 9th Circuit, "dcd" for DC District) |
limit | integer | — | Number of results (default 10, max 20) |
query | string | Yes | Search query for US court opinions (e.g. "artificial intelligence liability", "Fourth Amendment digital privacy") |
order_by | string | — | Sort: relevance (default), newest, oldest |
filed_after | string | — | Only cases filed after this date (YYYY-MM-DD) |
filed_before | string | — | Only cases filed before this date (YYYY-MM-DD) |
Parameters from the server's own tool schema.
Why legal.caselaw.search is rated Low
Retrieves publicly available court opinions without modifying or deleting data; no side effects.
From the tool's definition Search US federal and state court opinions — filter by court, date range, relevance.
Attacks that exploit this kind of access
The rule that runs legal.caselaw.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For legal.caselaw.search, this is the rule to start with:
legal.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 Apibase, apply this rule, and every legal.caselaw.search call is checked against it from then on.
Questions about legal.caselaw.search
Search US federal and state court opinions — filter by court (scotus, ca9, dcd...), date range, relevance. Largest free US case law archive. 7,000+ AI-related opinions (CourtListener / Free Law Project). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
legal.caselaw.search accepts 7 parameters: type, court, limit, query, order_by, filed_after, filed_before. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for legal.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 Apibase. Nothing to install.
legal.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 legal.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 legal.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.
legal.caselaw.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue