splitifi_judge_profile
Get behavioral profile for an indexed judge: grant rates, custody patterns, spousal support award rate, reversal rate. Pass the judge_id UUID from splitifi_find_judge, or pass a judge name directly for automatic lookup.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-judge-profile.md
What splitifi_judge_profile does on Splitifi Intelligence MCP
AI agents call splitifi_judge_profile 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_id | string | Yes | Splitifi judge ID (UUID) or judge name for automatic lookup |
Parameters from the server's own tool schema.
Why splitifi_judge_profile is rated Low
This is a pure data retrieval tool that queries an ML-indexed database of historical court records to surface behavioral statistics and patterns about judges. It has no write, delete, execute, or financial side effects.
From the tool's definition Tool retrieves judge behavioral profiles including 'grant rates, custody patterns, spousal support award rate, reversal rate' from indexed historical data.
Attacks that exploit this kind of access
The rule that runs splitifi_judge_profile 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_judge_profile, this is the rule to start with:
splitifi_judge_profile 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_judge_profile call is checked against it from then on.
Questions about splitifi_judge_profile
Get behavioral profile for an indexed judge: grant rates, custody patterns, spousal support award rate, reversal rate. Pass the judge_id UUID from splitifi_find_judge, or pass a judge name directly for automatic lookup. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_judge_profile accepts 1 parameter: judge_id. Required: judge_id. 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_judge_profile: 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_judge_profile 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_judge_profile 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_judge_profile. 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_judge_profile 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