splitifi_find_judge
Search for a judge by name, state, or county across 22,000+ indexed judges. Use this first when you have a judge's name but not their ID. Returns matching judges with court, case count, and judge_id for use with splitifi_judge_profile.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-find-judge.md
What splitifi_find_judge does on Splitifi Intelligence MCP
AI agents call splitifi_find_judge 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 |
|---|---|---|---|
name | string | — | Judge name or partial name (e.g. "Shull", "Karen Miller") |
state | string | — | Two-letter state code (e.g. "FL", "CA") |
county | string | — | County name (e.g. "Palm Beach", "Cook") |
Parameters from the server's own tool schema.
Why splitifi_find_judge is rated Low
This tool retrieves and queries data about judges from a public index. It has no side effects, does not modify data, does not execute external operations, and does not commit financial or destructive actions. It is a straightforward read/search operation used to locate judicial information prior to analysis by other tools (splitifi_judge_profile).
From the tool's definition Tool description states it 'Search[es] for a judge' and 'Returns matching judges' - purely retrieval operations with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
The rule that runs splitifi_find_judge 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 splitifi_find_judge, this is the rule to start with:
splitifi_find_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 Splitifi Intelligence MCP, apply this rule, and every splitifi_find_judge call is checked against it from then on.
Questions about splitifi_find_judge
Search for a judge by name, state, or county across 22,000+ indexed judges. Use this first when you have a judge's name but not their ID. Returns matching judges with court, case count, and judge_id for use with splitifi_judge_profile. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_find_judge accepts 3 parameters: name, state, county. 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 splitifi_find_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 Splitifi Intelligence MCP. Nothing to install.
splitifi_find_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 splitifi_find_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 splitifi_find_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.
splitifi_find_judge 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