splitifi_start
Start a guided Splitifi session. Declare your role (litigant, attorney, judge, mediator, paralegal, cdfa, forensic, gal, therapist), jurisdiction, and situation. Returns a personalized task plan and session_token to track progress. Optional — all tools work without it, but running this unlocks th...
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-start.md
What splitifi_start does on Splitifi Intelligence MCP
AI agents invoke splitifi_start to trigger actions in Splitifi Intelligence MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | Yes | Your role: litigant, attorney, judge, mediator, paralegal, cdfa, forensic, gal, therapist |
stage | string | — | Where you are: pre-filing, filed, discovery, trial, post-decree |
situation | string | — | One sentence describing the situation |
urgent_need | string | — | Most urgent thing you need help with right now |
jurisdiction | string | Yes | State or province code, e.g. "FL", "TX", "ON" |
Parameters from the server's own tool schema.
Why splitifi_start is rated High
splitifi_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs splitifi_start 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_start, this is the rule to start with:
splitifi_start stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_start call is checked against it from then on.
Questions about splitifi_start
Start a guided Splitifi session. Declare your role (litigant, attorney, judge, mediator, paralegal, cdfa, forensic, gal, therapist), jurisdiction, and situation. Returns a personalized task plan and session_token to track progress. Optional — all tools work without it, but running this unlocks the full guided experience. It is categorised as a Execute tool in the Splitifi Intelligence MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
splitifi_start accepts 5 parameters: role, stage, situation, urgent_need, jurisdiction. Required: role, 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_start: 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_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the splitifi_start 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_start. 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_start 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.
Across the catalogue