get_court
AI agents call get_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.
The tool retrieves court information from CourtListener's legal database with no indication of side effects, data modification, or external operations. Based on naming convention and sibling tools that are plainly read-only data retrieval operations, this is classified as Read. Confidence is slightly reduced due to lack of explicit description, but the pattern is clear.
From the tool's definition Tool name 'get_court' follows retrieval pattern consistent with sibling tools (get_docket, get_judge, get_opinion, get_cluster, get_educations) that fetch legal data without modification. Tool description is empty, limiting direct evidence.
Attacks that exploit this kind of access
get_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 get_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.
get_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 get_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 get_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.
get_court is provided by the CourtListener MCP Server MCP server (upsd1/courtlistener-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 →