splitifi_safety_planning
Get a safety planning checklist for situations involving domestic violence, coercive control, or concerns about the other party.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-safety-planning.md
What splitifi_safety_planning does on Splitifi Intelligence MCP
AI agents call splitifi_safety_planning 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 |
|---|---|---|---|
situation | string | — | Brief description of safety concern |
has_children | boolean | — | |
jurisdiction | string | — |
Parameters from the server's own tool schema.
Why splitifi_safety_planning is rated Low
The tool retrieves or generates informational content (a safety planning checklist) based on the user's situation context. There is no mention of modifying records, executing code, deleting data, or moving money. The tool functions as a reference or advisory resource rather than a system-altering operation. While the domain involves sensitive personal situations, the tool itself performs only informational tasks.
From the tool's definition Tool provides a 'checklist' for 'safety planning' in domestic violence situations. The description indicates information retrieval and guidance provision with no data modification, deletion, or financial transaction capability. This is a Read operation.
Attacks that exploit this kind of access
The rule that runs splitifi_safety_planning 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_safety_planning, this is the rule to start with:
splitifi_safety_planning 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_safety_planning call is checked against it from then on.
Questions about splitifi_safety_planning
Get a safety planning checklist for situations involving domestic violence, coercive control, or concerns about the other party. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_safety_planning accepts 3 parameters: situation, has_children, 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_safety_planning: 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_safety_planning 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_safety_planning 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_safety_planning. 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_safety_planning 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