court_filings_multi

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/court-filings-multi.md

WHAT IT DOES

What court_filings_multi does on Mcp Knowledge

AI agents call court_filings_multi to retrieve information from Mcp Knowledge 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
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`date_to`	string	—	ISO date YYYY-MM-DD — latest filing or decision date to include
`date_from`	string	—	ISO date YYYY-MM-DD — earliest filing or decision date to include
`party_name`	string	Yes	Name of the company or individual to search (e.g. "Apple Inc", "TotalEnergies", "Volkswagen AG")
`jurisdiction`	array	—	Jurisdictions to search. Defaults to all ["US","UK","EU","FR","DE"].

Parameters from the server's own tool schema.

RISK

Why court_filings_multi is rated Low

The tool retrieves and aggregates publicly available legal records from multiple jurisdictions without modifying any data. It is a read/query operation. Severity is medium because aggregating litigation records across jurisdictions for a company or individual could expose sensitive legal histories and enable misuse such as reputational harm or competitive intelligence abuse.

From the tool's definition Aggregate court filings, judgments and litigation records... Returns structured case records... opinion URLs and verbatim snippets

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs court_filings_multi safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For court_filings_multi, this is the rule to start with:

court_filings_multi Allowed

court_filings_multi is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "court_filings_multi": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every court_filings_multi call is checked against it from then on.

FAQ

Questions about court_filings_multi

What does the court_filings_multi tool do? +

Aggregate court filings, judgments and litigation records for a company or individual across five major legal jurisdictions: US (CourtListener / PACER), UK (National Archives — EWHC/EWCA/UKSC/UKUT), EU (ECHR HUDOC — European Court of Human Rights), France (Légifrance / Cour de cassation) and Germany (BGH / BVerfG). Returns structured case records with type classification (civil/criminal/antitrust/bankruptcy/administrative/unknown), status (filed/pending/decided/appealed/unknown), parties extracted from case titles, opinion URLs and verbatim snippets. Cross-case pattern recognition produces severity-ranked signals (P0–P2) for criminal, antitrust, bankruptcy, regulatory, data-breach and IP categories. Use when: due diligence on a counterparty, vendor risk assessment, competitive intelligence (litigation history), regulatory exposure mapping. All sources are public and keyless. Optional env var COURTLISTENER_API_KEY raises US rate limits beyond the default 5 req/s anonymous tier. SLA: ≤25s p95 (all jurisdictions fetched in parallel, 8s budget per source). Quality score: 20 pts per jurisdiction with ≥1 case retrieved, +10 if signals detected, +5–10 if ≥2–3 distinct sources contributed. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does court_filings_multi accept? +

court_filings_multi accepts 5 parameters: async, date_to, date_from, party_name, jurisdiction. Required: party_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on court_filings_multi? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for court_filings_multi: 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 Mcp Knowledge. Nothing to install.

What risk level is court_filings_multi? +

court_filings_multi is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit court_filings_multi? +

Yes. Add a rate_limit block to the court_filings_multi 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.

How do I block court_filings_multi completely? +

Set action: deny in the PolicyLayer policy for court_filings_multi. 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.

What MCP server provides court_filings_multi? +

court_filings_multi is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →