splitifi_timeline
Estimate the timeline for your divorce case from now to final decree. Returns weeks remaining, key milestones, and what drives the timeline.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-timeline.md
What splitifi_timeline does on Splitifi Intelligence MCP
AI agents call splitifi_timeline 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 |
|---|---|---|---|
stage | string | — | Current stage: pre-filing, filed, discovery, trial, post-decree |
has_children | boolean | — | |
jurisdiction | string | Yes | State/province code |
contested_level | string | — |
Parameters from the server's own tool schema.
Why splitifi_timeline is rated Low
This tool retrieves predictive information derived from ML models trained on historical court records. It queries data to provide timeline estimates for a divorce case. There are no side effects, no data modifications, no code execution, no financial transactions, and no destructive operations. The output is read-only predictions and analysis. This is a straightforward Read category tool.
From the tool's definition Tool description states it 'Estimate[s] the timeline' and 'Returns weeks remaining, key milestones, and what drives the timeline' — purely informational output with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs splitifi_timeline 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_timeline, this is the rule to start with:
splitifi_timeline 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_timeline call is checked against it from then on.
Questions about splitifi_timeline
Estimate the timeline for your divorce case from now to final decree. Returns weeks remaining, key milestones, and what drives the timeline. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_timeline accepts 4 parameters: stage, has_children, jurisdiction, contested_level. 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_timeline: 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_timeline 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_timeline 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_timeline. 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_timeline 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