splitifi_predict_custody
Predict custody outcome (sole vs joint, parenting time percentage) using ML models trained on 3.52B+ court records. Provide jurisdiction, optional judge_id, and case_facts describing the situation.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-predict-custody.md
What splitifi_predict_custody does on Splitifi Intelligence MCP
AI agents call splitifi_predict_custody 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 |
|---|---|---|---|
county | string | — | County name for local court data |
judge_id | string | — | Judge ID for judge-specific prediction |
case_facts | object | Yes | Case details: marriage_length_years, num_children, income_disparity, domestic_violence, relocation, etc. |
jurisdiction | string | Yes | State/province code, e.g. "TX", "ON" |
Parameters from the server's own tool schema.
Why splitifi_predict_custody is rated Low
This tool queries a pre-trained ML model to retrieve outcome predictions for custody cases. It is a read-only operation that returns data (predictions) without creating, modifying, deleting, or executing any external actions.
From the tool's definition Tool name and description indicate it 'Predict[s] custody outcome' using ML models trained on court records. No modification, deletion, or execution of external systems occurs. The tool retrieves predictions based on input case facts.
Attacks that exploit this kind of access
The rule that runs splitifi_predict_custody 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_predict_custody, this is the rule to start with:
splitifi_predict_custody 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_predict_custody call is checked against it from then on.
Questions about splitifi_predict_custody
Predict custody outcome (sole vs joint, parenting time percentage) using ML models trained on 3.52B+ court records. Provide jurisdiction, optional judge_id, and case_facts describing the situation. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_predict_custody accepts 4 parameters: county, judge_id, case_facts, jurisdiction. Required: case_facts, 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_predict_custody: 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_predict_custody 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_predict_custody 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_predict_custody. 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_predict_custody 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