splitifi_search_forms
Search forms by keyword across a jurisdiction. Useful when you know the form name or number but not the ID.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-search-forms.md
What splitifi_search_forms does on Splitifi Intelligence MCP
AI agents call splitifi_search_forms 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 |
|---|---|---|---|
limit | number | — | Max results. Default: 20 |
query | string | Yes | Search term, e.g. "petition for dissolution" or "Form 8A" |
country | string | — | |
state_province | string | — |
Parameters from the server's own tool schema.
Why splitifi_search_forms is rated Low
This tool retrieves form information (name, number, ID mappings) based on keyword input. It has no side effects, does not execute code or trigger external operations, does not create or modify data, and does not delete or move data.
From the tool's definition Tool description states 'Search forms by keyword across a jurisdiction' — a query/search operation with no modification, deletion, or execution capabilities. The verb 'search' and the passive retrieval of form metadata align with Read category.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs splitifi_search_forms 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_search_forms, this is the rule to start with:
splitifi_search_forms 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_search_forms call is checked against it from then on.
Questions about splitifi_search_forms
Search forms by keyword across a jurisdiction. Useful when you know the form name or number but not the ID. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_search_forms accepts 4 parameters: limit, query, country, state_province. Required: query. 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_search_forms: 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_search_forms 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_search_forms 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_search_forms. 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_search_forms 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