eoir_judge_screen
Profile an EOIR immigration judge. Returns grant rate, denial rate, removal rate, representation rate, represented grant rate, top courts, and top nationalities heard.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/eoir-judge-screen.md
What eoir_judge_screen does on Splitifi Intelligence MCP
AI agents call eoir_judge_screen to retrieve information from Splitifi Intelligence MCP 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 |
|---|---|---|---|
judge_name | string | Yes | Immigration judge full name or partial name |
Parameters from the server's own tool schema.
Why eoir_judge_screen is rated Low
This tool performs statistical retrieval and profiling of publicly available court decision patterns. It queries aggregated data from trained ML models on historical records and returns read-only insights (rates, rankings, demographics). There are no side effects, no data modification, no code execution, and no irreversible actions.
From the tool's definition Tool returns judge profile data including 'grant rate, denial rate, removal rate, representation rate, represented grant rate, top courts, and top nationalities heard' — all queries that retrieve and aggregate historical court records without modifying,…
Attacks that exploit this kind of access
The rule that runs eoir_judge_screen safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Splitifi Intelligence MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eoir_judge_screen, this is the rule to start with:
eoir_judge_screen 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 Splitifi Intelligence MCP, apply this rule, and every eoir_judge_screen call is checked against it from then on.
Questions about eoir_judge_screen
Profile an EOIR immigration judge. Returns grant rate, denial rate, removal rate, representation rate, represented grant rate, top courts, and top nationalities heard. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
eoir_judge_screen accepts 1 parameter: judge_name. Required: judge_name. The full parameter table on this page comes from the server's own tool schema.
Register the Splitifi Intelligence MCP server in PolicyLayer and add a rule for eoir_judge_screen: 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 Splitifi Intelligence MCP. Nothing to install.
eoir_judge_screen 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 eoir_judge_screen 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 eoir_judge_screen. 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.
eoir_judge_screen is provided by the Splitifi Intelligence MCP server (splitifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Splitifi Intelligence, and thousands of servers like it.
This server
Across the catalogue