caselaw_case_details
Get full metadata for a single case by its CAP id (name, citations, court, jurisdiction, decision date, reporter location, and the source URL for its full text).
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/caselaw-case-details.md
What caselaw_case_details does on Livedatalink
AI agents call caselaw_case_details 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 |
|---|---|---|---|
id | number | Yes | CAP case id, e.g. 11301409 (Brown v. Board of Education). |
Parameters from the server's own tool schema.
Why caselaw_case_details is rated Low
The tool performs a pure read operation that queries public legal case information and returns metadata. There are no side effects, no data modification, no code execution, and no deletion. The data retrieved appears to be from public caselaw databases (CAP format is a standard public legal archive format). This is a straightforward retrieval tool with minimal security risk in the context of an AI agent.
From the tool's definition Tool retrieves full metadata for a single case including name, citations, court, jurisdiction, decision date, reporter location, and source URL—all querying and retrieval operations with no modification or deletion capabilities.
Attacks that exploit this kind of access
The rule that runs caselaw_case_details 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_case_details, this is the rule to start with:
caselaw_case_details 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_case_details call is checked against it from then on.
Questions about caselaw_case_details
Get full metadata for a single case by its CAP id (name, citations, court, jurisdiction, decision date, reporter location, and the source URL for its full text). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
caselaw_case_details accepts 1 parameter: id. Required: id. 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_case_details: 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_case_details 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_case_details 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_case_details. 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_case_details 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