splitifi_post_decree_checklist
Get the post-divorce checklist: name change, beneficiary updates, asset retitling, insurance changes, estate planning.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-post-decree-checklist.md
What splitifi_post_decree_checklist does on Splitifi Intelligence MCP
AI agents call splitifi_post_decree_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 |
|---|---|---|---|
changed_name | boolean | — | |
has_children | boolean | — | |
has_property | boolean | — | |
jurisdiction | string | — |
Parameters from the server's own tool schema.
Why splitifi_post_decree_checklist is rated Low
The tool fetches a static or generated checklist of post-divorce administrative steps (name change, beneficiary updates, asset retitling, etc.). It is purely informational/advisory with no write, execute, or financial operations. Misuse risk is low as it only surfaces guidance.
From the tool's definition 'Get the post-divorce checklist' — retrieves a checklist of recommended actions; no side effects implied
Attacks that exploit this kind of access
The rule that runs splitifi_post_decree_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_post_decree_checklist, this is the rule to start with:
splitifi_post_decree_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_post_decree_checklist call is checked against it from then on.
Questions about splitifi_post_decree_checklist
Get the post-divorce checklist: name change, beneficiary updates, asset retitling, insurance changes, estate planning. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_post_decree_checklist accepts 4 parameters: changed_name, has_children, has_property, 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_post_decree_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_post_decree_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_post_decree_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_post_decree_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_post_decree_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