# submit_order

Submit a real formation order to FilingDesk. THIS HAS A REAL-WORLD EFFECT: it creates an order and notifies a FilingDesk specialist. Only call after preview_order and after the user has explicitly confirmed the summary. Nothing is charged now — a specialist reviews the order, verifies the name, and emails a payment link. Returns the order reference.

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

## Facts

- Tool: `submit_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: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 8 (6 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `email` | string | yes | The customer's email. |
| `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", or "Not sure". |
| `description` | string | no | What the business does. Optional. |
| `businessName` | string | yes | Proposed company name. |
| `userConfirmed` | boolean | yes | Must be true. Set only after the user has seen the preview_order summary and explicitly agreed to submit. |

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": "submit_order",
    "arguments": {
      "email": "<email>",
      "state": "<state>",
      "fullName": "<fullName>",
      "entityType": "<entityType>",
      "businessName": "<businessName>",
      "userConfirmed": false
    }
  }
}
```

## Why submit_order is rated Medium

An AI agent can call submit_order faster than any human can review: one bad instruction and it creates or modifies resources in FilingDesk Data by the hundred, each call as confident as the last.

## Use case

AI agents use submit_order to create or update resources in FilingDesk Data, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FilingDesk Data environment.

## 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": {
    "submit_order": {
      "limits": [
        {
          "counter": "submit_order_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on FilingDesk Data (7)

- `preview_order` — Execute — https://policylayer.com/tools/com-filingdesk-data/preview-order.md
- `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

## 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