compare_formation_options
Factual tradeoffs to help someone decide WHERE to form or WHAT entity type to pick. Returns fixed comparative facts and a required disclaimer — deliberately NOT a recommendation. Present the options neutrally, relay the disclaimer, and let the user choose; a FilingDesk specialist confirms the cho...
This record as markdown: /tools/com-filingdesk-data/compare-formation-options.md
What compare_formation_options does on FilingDesk Data
AI agents call compare_formation_options to retrieve information from FilingDesk Data 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 |
|---|---|---|---|
topic | string | Yes | "state" for where to form, "entity_type" for LLC vs S-corp vs C-corp. |
homeState | string | — | Optional. The state the user actually lives or operates in — lets the comparison include their home-state costs, which usually matter most. |
Parameters from the server's own tool schema.
Why compare_formation_options is rated Low
Even though compare_formation_options only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs compare_formation_options safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FilingDesk Data, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_formation_options, this is the rule to start with:
compare_formation_options 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 FilingDesk Data, apply this rule, and every compare_formation_options call is checked against it from then on.
Questions about compare_formation_options
Factual tradeoffs to help someone decide WHERE to form or WHAT entity type to pick. Returns fixed comparative facts and a required disclaimer — deliberately NOT a recommendation. Present the options neutrally, relay the disclaimer, and let the user choose; a FilingDesk specialist confirms the choice before anything is filed. It is categorised as a Read tool in the FilingDesk Data MCP Server, which means it retrieves data without modifying state.
compare_formation_options accepts 2 parameters: topic, homeState. Required: topic. The full parameter table on this page comes from the server's own tool schema.
Register the FilingDesk Data MCP server in PolicyLayer and add a rule for compare_formation_options: 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 FilingDesk Data. Nothing to install.
compare_formation_options 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 compare_formation_options 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 compare_formation_options. 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.
compare_formation_options is provided by the FilingDesk Data MCP server (https://filingdesk.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FilingDesk Data, and thousands of servers like it.
This server
Across the catalogue