splitifi_client_intake
Run a structured intake for a new family law client. Returns the key information to gather, questions to ask, and initial case assessment.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-client-intake.md
What splitifi_client_intake does on Splitifi Intelligence MCP
AI agents call splitifi_client_intake 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 |
|---|---|---|---|
case_type | string | — | |
jurisdiction | string | Yes | |
client_situation | string | — | Brief description from client |
Parameters from the server's own tool schema.
Why splitifi_client_intake is rated Low
The tool runs a structured intake process and returns informational output (questions, gathered info, initial assessment). There is no indication it writes to a database, executes code, deletes data, or involves financial transactions. It behaves as a query/read operation that generates a structured response.
From the tool's definition 'Returns the key information to gather, questions to ask, and initial case assessment' — the tool produces structured output/assessment without indicating any data persistence or side effects
Attacks that exploit this kind of access
The rule that runs splitifi_client_intake 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_client_intake, this is the rule to start with:
splitifi_client_intake 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_client_intake call is checked against it from then on.
Questions about splitifi_client_intake
Run a structured intake for a new family law client. Returns the key information to gather, questions to ask, and initial case assessment. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_client_intake accepts 3 parameters: case_type, jurisdiction, client_situation. 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_client_intake: 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_client_intake 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_client_intake 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_client_intake. 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_client_intake 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