AI agents call list_recent_cases to retrieve information from Legal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing legal opinion data from CourtListener without creating, modifying, deleting, or executing any operations. It has no side effects beyond returning information. The blast radius of misuse is minimal—an agent could retrieve irrelevant or excessive legal records, but no data would be harmed, financial obligations triggered, or external operations executed.
From the tool's definition Tool description states 'List the newest opinions in a court, most recent first' — a retrieval operation with no mutation. Tool name 'list_recent_cases' and sibling tools like 'get_case', 'search_cases', 'read_opinion' all indicate read-only access patterns.
Attacks that exploit this kind of access
List the newest opinions in a court, most recent first. It is categorised as a Read tool in the Legal MCP Server, which means it retrieves data without modifying state.
Register the Legal MCP server in PolicyLayer and add a rule for list_recent_cases: 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 Legal. Nothing to install.
list_recent_cases 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 list_recent_cases 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 list_recent_cases. 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.
list_recent_cases is provided by the Legal MCP server (mcpservings/legal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →