splitifi_trial_readiness
Score trial readiness and identify gaps: documents, witnesses, experts, discovery completion.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-trial-readiness.md
What splitifi_trial_readiness does on Splitifi Intelligence MCP
AI agents call splitifi_trial_readiness 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 | — | |
documents_ready | boolean | — | |
expert_retained | boolean | — | |
witnesses_identified | boolean | — |
Parameters from the server's own tool schema.
Why splitifi_trial_readiness is rated Low
This tool performs read-only analysis of trial preparation status by reviewing documents, witnesses, experts, and discovery completion. It generates insights and scores but does not create, modify, delete, or execute any irreversible actions.
From the tool's definition Tool description states it 'Score trial readiness and identify gaps' - a purely analytical assessment function that retrieves or analyzes existing case information.
Attacks that exploit this kind of access
The rule that runs splitifi_trial_readiness 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_trial_readiness, this is the rule to start with:
splitifi_trial_readiness 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_trial_readiness call is checked against it from then on.
Questions about splitifi_trial_readiness
Score trial readiness and identify gaps: documents, witnesses, experts, discovery completion. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_trial_readiness accepts 4 parameters: case_facts, documents_ready, expert_retained, witnesses_identified. 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_trial_readiness: 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_trial_readiness 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_trial_readiness 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_trial_readiness. 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_trial_readiness 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