# preview_order

Build an exact order summary WITHOUT submitting anything. No side effects. Validates the details, prices the order, and returns a confirmation summary. ALWAYS call this and show the user the returned summary before calling submit_order.

Agent View of the PolicyLayer registry record for `preview_order`. HTML page: https://policylayer.com/tools/com-filingdesk-data/preview-order

## Facts

- Tool: `preview_order`
- Server: FilingDesk Data (`https://filingdesk.com/api/mcp`) — https://policylayer.com/tools/com-filingdesk-data.md
- Homepage: https://github.com/https://filingdesk.com/api/mcp
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 7 (5 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `email` | string | yes | The customer's email. Required — this is how they are contacted. |
| `phone` | string | no | Optional phone number. |
| `state` | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
| `fullName` | string | yes | The customer's full name. |
| `entityType` | string | yes | Entity type, e.g. "LLC", "S-Corp", "C-Corp", or "Not sure" if the user hasn't decided. |
| `description` | string | no | One or two sentences on what the business does. Optional — the user may skip it. |
| `businessName` | string | yes | Proposed company name. Does not need to be final — a specialist verifies availability. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "preview_order",
    "arguments": {
      "email": "<email>",
      "state": "<state>",
      "fullName": "<fullName>",
      "entityType": "<entityType>",
      "businessName": "<businessName>"
    }
  }
}
```

## Why preview_order is rated High

preview_order triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke preview_order to trigger actions in FilingDesk Data. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FilingDesk Data:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "preview_order": {
      "limits": [
        {
          "counter": "preview_order_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on FilingDesk Data (7)

- `check_llc_name` — Read — https://policylayer.com/tools/com-filingdesk-data/check-llc-name.md
- `compare_formation_options` — Read — https://policylayer.com/tools/com-filingdesk-data/compare-formation-options.md
- `compare_llc_costs` — Read — https://policylayer.com/tools/com-filingdesk-data/compare-llc-costs.md
- `get_annual_report_deadline` — Read — https://policylayer.com/tools/com-filingdesk-data/get-annual-report-deadline.md
- `get_llc_fees` — Read — https://policylayer.com/tools/com-filingdesk-data/get-llc-fees.md
- `list_filing_states` — Read — https://policylayer.com/tools/com-filingdesk-data/list-filing-states.md
- `submit_order` — Write — https://policylayer.com/tools/com-filingdesk-data/submit-order.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-filingdesk-data · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-filingdesk-data