court_judge_lookup
Look up a judge profile by name or CourtListener person ID. Returns positions, education, and bench history.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/court-judge-lookup.md
What court_judge_lookup does on Livedatalink
AI agents call court_judge_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 |
|---|---|---|---|
name | string | Yes | Judge full or partial name, or numeric person ID. |
Parameters from the server's own tool schema.
Why court_judge_lookup is rated Low
This tool retrieves and queries publicly available judicial information (judge profiles, positions, education, bench history) without side effects. It is a straightforward data lookup operation that does not create, modify, delete, or execute any actions. The low severity reflects minimal risk even if misused by an agent, as it only exposes public judicial records.
From the tool's definition Tool performs 'Look up' operation returning 'positions, education, and bench history' - purely informational retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs court_judge_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_judge_lookup, this is the rule to start with:
court_judge_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_judge_lookup call is checked against it from then on.
Questions about court_judge_lookup
Look up a judge profile by name or CourtListener person ID. Returns positions, education, and bench history. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
court_judge_lookup accepts 1 parameter: name. Required: name. 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_judge_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_judge_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_judge_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_judge_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_judge_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