Get full details of a specific court opinion by its ID.
AI agents call get_case_details to retrieve information from LegalMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries court opinion data by ID without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no side effects, matching the 'Read' category definition. Severity is low because unauthorized access to publicly available court opinions presents minimal risk and does not enable destructive or financial harm.
From the tool's definition Tool name 'get_case_details' and description 'Get full details of a specific court opinion by its ID' indicate retrieval of existing case information with no modification, deletion, or execution of commands.
Documented attack patterns abuse exactly the kind of access get_case_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LegalMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_case_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_case_details": {}
}
}get_case_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get full details of a specific court opinion by its ID. It is categorised as a Read tool in the LegalMCP MCP Server, which means it retrieves data without modifying state.
Register the Legal MCP server in PolicyLayer and add a rule for get_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 LegalMCP. Nothing to install.
get_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 get_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 get_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.
get_case_details is provided by the Legal MCP server (mahender22/legal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LegalMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 LegalMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.