splitifi_strategy_core
Ranked strategy paths for Core Prediction cases — probability of success, estimated cost, and timeline for each path (negotiation, litigation, ADR).
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-strategy-core.md
What splitifi_strategy_core does on Splitifi Intelligence MCP
AI agents call splitifi_strategy_core 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 | Yes | Case details for Core Prediction. Key fields: case_type, jurisdiction, complexity, procedural_stage, risk_factors |
jurisdiction | string | Yes | State/province code |
Parameters from the server's own tool schema.
Why splitifi_strategy_core is rated Low
This tool queries ML models trained on court records to generate ranked strategy recommendations with associated metrics. While the *consequences* of following its advice could be financial or involve execution (if a user acts on the recommendations), the tool itself only reads data and returns predictions/rankings.
From the tool's definition Tool retrieves and ranks 'strategy paths' with predictions (probability, cost, timeline) for cases. No mutations, deletions, executions, or financial transactions are performed by the tool itself — it provides analysis and estimates.
Attacks that exploit this kind of access
The rule that runs splitifi_strategy_core 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_strategy_core, this is the rule to start with:
splitifi_strategy_core 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_strategy_core call is checked against it from then on.
Questions about splitifi_strategy_core
Ranked strategy paths for Core Prediction cases — probability of success, estimated cost, and timeline for each path (negotiation, litigation, ADR). It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_strategy_core accepts 2 parameters: case_facts, jurisdiction. Required: case_facts, 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_strategy_core: 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_strategy_core 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_strategy_core 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_strategy_core. 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_strategy_core 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