splitifi_get_checklist
Get a full checklist with all items, priorities, and jurisdiction-specific notes. Use splitifi_list_checklists to discover available checklist IDs.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-get-checklist.md
What splitifi_get_checklist does on Splitifi Intelligence MCP
AI agents call splitifi_get_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 |
|---|---|---|---|
checklist_id | string | Yes | Checklist ID, e.g. "pre-divorce", "financial-docs", "child-custody", "property-division", "post-divorce" |
jurisdiction | string | — | Optional state/province code for jurisdiction-specific notes |
Parameters from the server's own tool schema.
Why splitifi_get_checklist is rated Low
This tool retrieves checklist data from the service without any capability to create, modify, delete, or execute operations. It is a straightforward Read operation with minimal blast radius — misuse would only expose information, not cause irreversible harm or trigger external actions.
From the tool's definition The tool description states 'Get a full checklist with all items, priorities, and jurisdiction-specific notes' — this is a retrieval operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs splitifi_get_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_get_checklist, this is the rule to start with:
splitifi_get_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_get_checklist call is checked against it from then on.
Questions about splitifi_get_checklist
Get a full checklist with all items, priorities, and jurisdiction-specific notes. Use splitifi_list_checklists to discover available checklist IDs. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_get_checklist accepts 2 parameters: checklist_id, jurisdiction. Required: checklist_id. 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_get_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_get_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_get_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_get_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_get_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