splitifi_discovery_checklist
Get a complete discovery checklist for a family law matter: financial documents, interrogatories, depositions, and custody-specific discovery.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-discovery-checklist.md
What splitifi_discovery_checklist does on Splitifi Intelligence MCP
AI agents call splitifi_discovery_checklist 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 | — | |
has_business | boolean | — | |
jurisdiction | string | Yes | |
has_retirement | boolean | — |
Parameters from the server's own tool schema.
Why splitifi_discovery_checklist is rated Low
The tool retrieves or generates a checklist of discovery requirements for legal proceedings. This is fundamentally a read operation — it provides information/guidance without side effects.
From the tool's definition Tool description states "Get a complete discovery checklist" — this is a retrieval/query operation that returns information about what documents and interrogatories should be gathered in a family law matter. No data is created, modified, deleted, or executed.
Attacks that exploit this kind of access
The rule that runs splitifi_discovery_checklist 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_discovery_checklist, this is the rule to start with:
splitifi_discovery_checklist 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_discovery_checklist call is checked against it from then on.
Questions about splitifi_discovery_checklist
Get a complete discovery checklist for a family law matter: financial documents, interrogatories, depositions, and custody-specific discovery. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_discovery_checklist accepts 4 parameters: case_type, has_business, jurisdiction, has_retirement. 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_discovery_checklist: 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_discovery_checklist 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_discovery_checklist 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_discovery_checklist. 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_discovery_checklist 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