splitifi_case_summary
Get a full snapshot of your case: role, jurisdiction, situation, completed tasks, remaining steps, and what to do next.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-case-summary.md
What splitifi_case_summary does on Splitifi Intelligence MCP
AI agents call splitifi_case_summary 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 |
|---|---|---|---|
session_token | string | Yes | Your session token from splitifi_start |
Parameters from the server's own tool schema.
Why splitifi_case_summary is rated Low
This tool retrieves and queries case information without side effects, fitting the Read category. Severity is medium rather than low because the tool operates on legal case data that could inform high-stakes decisions (litigation strategy, arbitration outcomes) if an AI agent misuses the retrieved information in a chained operation.
From the tool's definition Tool description states 'Get a full snapshot of your case' with retrieval of case details including 'role, jurisdiction, situation, completed tasks, remaining steps, and what to do next.' No modification, deletion, or financial transaction is performed.
Attacks that exploit this kind of access
The rule that runs splitifi_case_summary 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_case_summary, this is the rule to start with:
splitifi_case_summary 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_case_summary call is checked against it from then on.
Questions about splitifi_case_summary
Get a full snapshot of your case: role, jurisdiction, situation, completed tasks, remaining steps, and what to do next. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_case_summary accepts 1 parameter: session_token. Required: session_token. 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_case_summary: 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_case_summary 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_case_summary 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_case_summary. 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_case_summary 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