splitifi_comparable_cases
Get outcome distributions from 2.5M+ comparable cases: settlement percentages, median timelines, cost ranges, custody split distributions.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-comparable-cases.md
What splitifi_comparable_cases does on Splitifi Intelligence MCP
AI agents call splitifi_comparable_cases 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 |
|---|---|---|---|
filters | object | — | Optional: marriage_length_range, asset_range, has_children, contested |
case_type | string | — | |
jurisdiction | string | Yes |
Parameters from the server's own tool schema.
Why splitifi_comparable_cases is rated Low
This tool queries and retrieves aggregated statistical outcomes from past legal cases to provide predictive insights. It performs a passive data retrieval with no side effects, no code execution, no data modification, and no destructive operations.
From the tool's definition Tool description states 'Get outcome distributions' and 'settlement percentages, median timelines, cost ranges, custody split distributions' — all read operations that retrieve historical data and statistics from a database of court records.
Attacks that exploit this kind of access
The rule that runs splitifi_comparable_cases 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_comparable_cases, this is the rule to start with:
splitifi_comparable_cases 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_comparable_cases call is checked against it from then on.
Questions about splitifi_comparable_cases
Get outcome distributions from 2.5M+ comparable cases: settlement percentages, median timelines, cost ranges, custody split distributions. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_comparable_cases accepts 3 parameters: filters, 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_comparable_cases: 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_comparable_cases 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_comparable_cases 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_comparable_cases. 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_comparable_cases 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