splitifi_ruling_patterns
Get statewide ruling patterns for a case type: custody split distributions, support award medians, property division norms.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-ruling-patterns.md
What splitifi_ruling_patterns does on Splitifi Intelligence MCP
AI agents call splitifi_ruling_patterns 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 | — | Optional — returns judge-specific patterns |
case_type | string | — | |
jurisdiction | string | Yes |
Parameters from the server's own tool schema.
Why splitifi_ruling_patterns is rated Low
This tool retrieves statistical patterns and norms derived from 30.3M court records. While it performs only read operations (no side effects), the severity is elevated to 'high' because the data—judicial ruling patterns on custody, support, and property division—could be misused to manipulate legal strategy, bias case presentations, or enable predatory litigation tactics if an AI agent weaponizes these predictions.
From the tool's definition Tool description states 'Get statewide ruling patterns' for custody, support, and property division outcomes. The verb 'Get' and the focus on retrieving aggregated patterns from court records indicates data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs splitifi_ruling_patterns 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_ruling_patterns, this is the rule to start with:
splitifi_ruling_patterns 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_ruling_patterns call is checked against it from then on.
Questions about splitifi_ruling_patterns
Get statewide ruling patterns for a case type: custody split distributions, support award medians, property division norms. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_ruling_patterns accepts 3 parameters: judge_id, case_type, jurisdiction. Required: jurisdiction. 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_ruling_patterns: 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_ruling_patterns 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_ruling_patterns 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_ruling_patterns. 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_ruling_patterns 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