splitifi_disparity_flags
Identify jurisdictional outcome disparities — cases where outcomes diverge significantly from statewide norms.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-disparity-flags.md
What splitifi_disparity_flags does on Splitifi Intelligence MCP
AI agents call splitifi_disparity_flags 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 |
|---|---|---|---|
filters | object | — | |
case_type | string | — | |
jurisdiction | string | Yes |
Parameters from the server's own tool schema.
Why splitifi_disparity_flags is rated Low
This tool retrieves and analyzes data from existing ML models to flag statistical disparities in judicial outcomes. It does not create, modify, delete, or execute external operations. While the subject matter involves sensitive legal/judicial data and could raise fairness concerns, the technical function is purely analytical/read-based.
From the tool's definition Tool performs analysis and identification of disparities through querying ML models trained on court records.
Attacks that exploit this kind of access
The rule that runs splitifi_disparity_flags 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_disparity_flags, this is the rule to start with:
splitifi_disparity_flags 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_disparity_flags call is checked against it from then on.
Questions about splitifi_disparity_flags
Identify jurisdictional outcome disparities — cases where outcomes diverge significantly from statewide norms. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_disparity_flags accepts 3 parameters: filters, case_type, 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_disparity_flags: 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_disparity_flags 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_disparity_flags 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_disparity_flags. 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_disparity_flags 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