courtlistener_search_cases_keyword
A read tool on the Courtlistener MCP server.
This record as markdown: /tools/defendthedisabled-courtlistener-mcp/courtlistener-search-cases-keyword.md
What courtlistener_search_cases_keyword does on Courtlistener
AI agents call courtlistener_search_cases_keyword 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_search_cases_keyword is rated Low
This tool performs keyword-based search across CourtListener's legal case database. Like its sibling search and get tools, it retrieves and queries data without modifying, deleting, or executing arbitrary code. The empty description is compensated by the clear naming convention and consistent pattern of read-only tools on the server.
From the tool's definition Tool name 'courtlistener_search_cases_keyword' indicates a search operation. All sibling tools on this server (courtlistener_get_case, courtlistener_search_cases_hybrid, courtlistener_search_cases_semantic, courtlistener_list_courts, etc.) are read-only query…
Attacks that exploit this kind of access
The rule that runs courtlistener_search_cases_keyword 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_search_cases_keyword, this is the rule to start with:
courtlistener_search_cases_keyword 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_search_cases_keyword call is checked against it from then on.
Questions about courtlistener_search_cases_keyword
courtlistener_search_cases_keyword 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_search_cases_keyword: 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_search_cases_keyword 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_search_cases_keyword 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_search_cases_keyword. 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_search_cases_keyword 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