courtlistener_list_courts
A read tool on the Courtlistener MCP server.
This record as markdown: /tools/defendthedisabled-courtlistener-mcp/courtlistener-list-courts.md
What courtlistener_list_courts does on Courtlistener
AI agents call courtlistener_list_courts to retrieve information from Courtlistener without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why courtlistener_list_courts is rated Low
The tool name 'list_courts' clearly performs a retrieval operation that returns a list of court information without modifying data. This fits the Read category: retrieves or queries data with no side effects. Confidence is slightly reduced (0.85 rather than 0.95+) because the description is empty, preventing direct confirmation, but the name and surrounding context strongly indicate a non-destructive query operation.
From the tool's definition Tool name 'courtlistener_list_courts' indicates a listing/enumeration operation. The broader server context shows it is part of CourtListener's legal database tools that provide "semantic search, hybrid search, citation verification, and research tools" — all…
Attacks that exploit this kind of access
The rule that runs courtlistener_list_courts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Courtlistener, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For courtlistener_list_courts, this is the rule to start with:
courtlistener_list_courts 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 Courtlistener, apply this rule, and every courtlistener_list_courts call is checked against it from then on.
Questions about courtlistener_list_courts
courtlistener_list_courts is a read tool on the Courtlistener MCP server. It is categorised as a Read tool in the Courtlistener MCP Server, which means it retrieves data without modifying state.
Register the Courtlistener MCP server in PolicyLayer and add a rule for courtlistener_list_courts: 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 Courtlistener. Nothing to install.
courtlistener_list_courts 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 courtlistener_list_courts 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 courtlistener_list_courts. 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.
courtlistener_list_courts is provided by the Courtlistener MCP server (defendthedisabled/courtlistener-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Courtlistener, and thousands of servers like it.
This server
Across the catalogue