get_docket
AI agents call get_docket 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.
This tool retrieves docket information—a read-only operation with no side effects. It queries existing legal data without modifying, executing code, deleting records, or creating financial obligations. The naming pattern matches other retrieval tools on this server. Confidence is moderately high despite empty description, based on context from sibling tools and the name's clear semantic meaning in legal research.
From the tool's definition Tool name 'get_docket' and server context indicate retrieval of legal case docket information from CourtListener's database. No description provided, but sibling tools (get_cluster, get_court, get_judge, etc.) are all read-only retrieval operations.
Attacks that exploit this kind of access
get_docket. 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_docket: 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_docket 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_docket 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_docket. 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_docket 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 →