courtlistener-get-judge
Fetch a CourtListener person (judge) by numeric id.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/courtlistener-get-judge.md
What courtlistener-get-judge does on Meta Data Mcp
AI agents call courtlistener-get-judge to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why courtlistener-get-judge is rated Low
This tool retrieves publicly available judicial information from CourtListener, an open legal database. It performs a simple lookup by ID without modifying data, executing code, deleting records, or committing financial transactions. The operation is read-only and returns structured data about judges. There is minimal blast radius even if misused—an agent could only retrieve additional public records, not cause harm.
From the tool's definition Tool name is 'courtlistener-get-judge' and description states 'Fetch a CourtListener person (judge) by numeric id.' The verb 'Fetch' and the retrieval of public judge information by identifier indicate a read-only query with no side effects.
Attacks that exploit this kind of access
The rule that runs courtlistener-get-judge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For courtlistener-get-judge, this is the rule to start with:
courtlistener-get-judge 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 Meta Data Mcp, apply this rule, and every courtlistener-get-judge call is checked against it from then on.
Questions about courtlistener-get-judge
Fetch a CourtListener person (judge) by numeric id. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for courtlistener-get-judge: 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 Meta Data Mcp. Nothing to install.
courtlistener-get-judge 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 courtlistener-get-judge 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 courtlistener-get-judge. 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.
courtlistener-get-judge is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue