splitifi_forensic_flags
Detect financial red flags in divorce disclosures: income suppression, pre-filing asset transfers, missing business valuations, lifestyle vs reported income gaps.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-forensic-flags.md
What splitifi_forensic_flags does on Splitifi Intelligence MCP
AI agents call splitifi_forensic_flags 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_facts | object | — | |
disclosure_data | object | Yes | Financial disclosure documents and reported values |
Parameters from the server's own tool schema.
Why splitifi_forensic_flags is rated Low
This tool performs forensic analysis and anomaly detection on structured financial data from legal proceedings. While the output (flagged disclosures) could inform high-stakes financial decisions in divorce proceedings, the tool itself only reads and analyzes existing disclosure data. It does not move funds, execute transactions, delete records, or trigger irreversible actions.
From the tool's definition Tool name is 'splitifi_forensic_flags'; description states it will 'Detect financial red flags' by analyzing 'income suppression, pre-filing asset transfers, missing business valuations, lifestyle vs reported income gaps' in divorce disclosures.
Attacks that exploit this kind of access
The rule that runs splitifi_forensic_flags 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_forensic_flags, this is the rule to start with:
splitifi_forensic_flags 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_forensic_flags call is checked against it from then on.
Questions about splitifi_forensic_flags
Detect financial red flags in divorce disclosures: income suppression, pre-filing asset transfers, missing business valuations, lifestyle vs reported income gaps. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_forensic_flags accepts 2 parameters: case_facts, disclosure_data. Required: disclosure_data. 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_forensic_flags: 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_forensic_flags 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_forensic_flags 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_forensic_flags. 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_forensic_flags 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