court_recent_filings
Recent docket entries filed in a specific court, ordered newest first.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/court-recent-filings.md
What court_recent_filings does on Livedatalink
AI agents call court_recent_filings 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', 'cand'. |
limit | number | — | Max results (1-50, default 10). |
Parameters from the server's own tool schema.
Why court_recent_filings is rated Low
This tool queries and returns publicly available court docket information. It has no side effects, does not modify data, execute code, delete anything, or move money. The operation is read-only retrieval of existing public records. Severity is low because docket entries are typically public information with no sensitive operational risk if misused by an agent.
From the tool's definition Tool retrieves 'Recent docket entries filed in a specific court, ordered newest first' — a query operation that returns public court records without modification.
Attacks that exploit this kind of access
The rule that runs court_recent_filings 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_recent_filings, this is the rule to start with:
court_recent_filings 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_recent_filings call is checked against it from then on.
Questions about court_recent_filings
Recent docket entries filed in a specific court, ordered newest first. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
court_recent_filings accepts 2 parameters: court, limit. Required: court. 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_recent_filings: 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_recent_filings 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_recent_filings 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_recent_filings. 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_recent_filings 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