splitifi_document_queue
Get a prioritized document preparation queue for a paralegal: which forms to prepare first, what information is needed, and filing sequence.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-document-queue.md
What splitifi_document_queue does on Splitifi Intelligence MCP
AI agents call splitifi_document_queue 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 |
|---|---|---|---|
stage | string | — | |
case_type | string | — | |
jurisdiction | string | Yes |
Parameters from the server's own tool schema.
Why splitifi_document_queue is rated Low
This tool queries data (a prioritization queue and paralegal guidance) without creating, modifying, or deleting records, executing code, or triggering financial transactions. It is informational/retrieval-only. The low severity reflects minimal blast radius—a misconfigured queue recommendation causes operational inefficiency but no irreversible damage or unauthorized access.
From the tool's definition Tool retrieves and prioritizes a document queue with recommendations: 'which forms to prepare first, what information is needed, and filing sequence.' No modification, deletion, or execution of external systems occurs; the output is advisory guidance only.
Attacks that exploit this kind of access
The rule that runs splitifi_document_queue 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_document_queue, this is the rule to start with:
splitifi_document_queue 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_document_queue call is checked against it from then on.
Questions about splitifi_document_queue
Get a prioritized document preparation queue for a paralegal: which forms to prepare first, what information is needed, and filing sequence. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_document_queue accepts 3 parameters: stage, 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_document_queue: 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_document_queue 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_document_queue 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_document_queue. 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_document_queue 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