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.
This record as markdown: /tools/com-filingdesk-data/preview-order.md
What preview_order does on FilingDesk Data
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | The customer's email. Required — this is how they are contacted. |
phone | string | — | 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 | — | 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.
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.
Attacks that exploit this kind of access
The rule that runs preview_order 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 preview_order, this is the rule to start with:
preview_order stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 preview_order call is checked against it from then on.
Questions about 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. It is categorised as a Execute tool in the FilingDesk Data MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
preview_order accepts 7 parameters: email, phone, state, fullName, entityType, description, businessName. Required: email, state, fullName, entityType, businessName. 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 preview_order: 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.
preview_order is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the preview_order 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 preview_order. 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.
preview_order 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.
Across the catalogue