AI agents call court to retrieve information from CourtListener MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on context of a legal research database server where all documented sibling tools perform read-only retrieval operations, this tool almost certainly queries court information without side effects. The empty description reduces confidence slightly, but the sibling tool pattern strongly indicates a read operation with minimal security risk.
From the tool's definition Tool name 'court' with empty description suggests querying court data from CourtListener's legal database.
Documented attack patterns abuse exactly the kind of access court gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CourtListener MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for court:
{
"version": "1",
"default": "deny",
"tools": {
"court": {}
}
}court 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.
court. It is categorised as a Read tool in the CourtListener MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CourtListener MCP Server MCP server in PolicyLayer and add a rule for court: 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 MCP Server. Nothing to install.
court 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 court 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 court. 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.
court is provided by the CourtListener MCP Server MCP server (travis-prall/court-listener-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CourtListener MCP Server, 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 CourtListener MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.