court_docket_lookup
Look up a federal docket by court ID and docket number. Returns party list and recent entries from PACER/RECAP.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/court-docket-lookup.md
What court_docket_lookup does on Livedatalink
AI agents call court_docket_lookup to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
court | string | Yes | Court ID, e.g. 'nysd'. |
docket_number | string | Yes | Docket number, e.g. '1:23-cv-04567'. |
Parameters from the server's own tool schema.
Why court_docket_lookup is rated Low
This tool retrieves and queries existing public court docket information without creating, modifying, deleting, or executing anything. It is clearly a Read operation. Severity is medium rather than low because court docket information can contain sensitive personal details (party names, addresses, case facts), and unrestricted access could enable privacy violations or targeted harassment, though the data itself is…
From the tool's definition Tool description states it 'Look[s] up' and 'Returns' data from federal dockets—these are query/retrieval operations with no modification or deletion. Accesses public legal records via PACER/RECAP.
Attacks that exploit this kind of access
The rule that runs court_docket_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For court_docket_lookup, this is the rule to start with:
court_docket_lookup 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 Livedatalink, apply this rule, and every court_docket_lookup call is checked against it from then on.
Questions about court_docket_lookup
Look up a federal docket by court ID and docket number. Returns party list and recent entries from PACER/RECAP. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
court_docket_lookup accepts 2 parameters: court, docket_number. Required: court, docket_number. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for court_docket_lookup: 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 Livedatalink. Nothing to install.
court_docket_lookup 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_docket_lookup 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_docket_lookup. 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_docket_lookup is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue