splitifi_custody_schedule
Get common custody schedule options (2-2-3, week-on-week-off, etc.) with pros/cons for each based on children's ages.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-custody-schedule.md
What splitifi_custody_schedule does on Splitifi Intelligence MCP
AI agents call splitifi_custody_schedule 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 |
|---|---|---|---|
jurisdiction | string | Yes | |
num_children | number | — | |
youngest_age | number | — | Age of youngest child |
parent_work_schedules | string | — | Describe each parent's work schedule |
Parameters from the server's own tool schema.
Why splitifi_custody_schedule is rated Low
This tool retrieves and presents informational content about custody schedule options. It performs a read/query operation returning structured data with no side effects, writes, or external triggers. The tool simply fetches predefined schedule patterns and associated analysis based on input parameters.
From the tool's definition 'Get common custody schedule options' with 'pros/cons for each based on children's ages'
Attacks that exploit this kind of access
The rule that runs splitifi_custody_schedule 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_custody_schedule, this is the rule to start with:
splitifi_custody_schedule 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_custody_schedule call is checked against it from then on.
Questions about splitifi_custody_schedule
Get common custody schedule options (2-2-3, week-on-week-off, etc.) with pros/cons for each based on children's ages. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_custody_schedule accepts 4 parameters: jurisdiction, num_children, youngest_age, parent_work_schedules. 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_custody_schedule: 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_custody_schedule 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_custody_schedule 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_custody_schedule. 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_custody_schedule 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