splitifi_deadline_tracker
Get key case deadlines from filing date: service, answer, discovery cutoff, mediation, pretrial, trial.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-deadline-tracker.md
What splitifi_deadline_tracker does on Splitifi Intelligence MCP
AI agents call splitifi_deadline_tracker 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_type | string | — | |
filing_date | string | — | ISO date string, e.g. "2026-04-01" |
jurisdiction | string | Yes |
Parameters from the server's own tool schema.
Why splitifi_deadline_tracker is rated Low
This tool retrieves and queries case deadline data derived from court records based on a filing date input. It has no side effects—it does not create, modify, delete, or execute operations. It simply reads and returns existing deadline information from the ML model's training data.
From the tool's definition Tool name 'splitifi_deadline_tracker' and description 'Get key case deadlines from filing date' indicate retrieval of deadline information. The verb 'Get' and the absence of any mutation, deletion, or execution language confirm this is a query operation.
Attacks that exploit this kind of access
The rule that runs splitifi_deadline_tracker 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_deadline_tracker, this is the rule to start with:
splitifi_deadline_tracker 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_deadline_tracker call is checked against it from then on.
Questions about splitifi_deadline_tracker
Get key case deadlines from filing date: service, answer, discovery cutoff, mediation, pretrial, trial. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_deadline_tracker accepts 3 parameters: case_type, filing_date, jurisdiction. 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_deadline_tracker: 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_deadline_tracker 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_deadline_tracker 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_deadline_tracker. 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_deadline_tracker 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