splitifi_asset_tracing
Get an asset tracing workflow for suspected hidden assets: steps, document requests, red flags to look for.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-asset-tracing.md
What splitifi_asset_tracing does on Splitifi Intelligence MCP
AI agents call splitifi_asset_tracing 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 | |
suspected_issues | array | — | e.g. ["income suppression", "pre-filing transfers", "business undervaluation"] |
total_estate_value | number | — |
Parameters from the server's own tool schema.
Why splitifi_asset_tracing is rated Low
This tool retrieves and presents investigative guidance and procedural information from trained ML models. It does not create, modify, delete, or execute any action on assets, financial systems, or external services. The output is read-only advisory information intended to support human decision-making in asset tracing workflows.
From the tool's definition Tool description states it provides 'steps, document requests, red flags to look for' — informational guidance and workflow recommendations for asset tracing investigations. No mutation, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs splitifi_asset_tracing 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_asset_tracing, this is the rule to start with:
splitifi_asset_tracing 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_asset_tracing call is checked against it from then on.
Questions about splitifi_asset_tracing
Get an asset tracing workflow for suspected hidden assets: steps, document requests, red flags to look for. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_asset_tracing accepts 3 parameters: jurisdiction, suspected_issues, total_estate_value. 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_asset_tracing: 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_asset_tracing 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_asset_tracing 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_asset_tracing. 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_asset_tracing 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