submit_order

SERVERFilingDesk Data SOURCEhttps://filingdesk.com/api/mcp

Medium RISK CLASS

Category Write

Parameters 86 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-filingdesk-data/submit-order.md

WHAT IT DOES

What submit_order does on FilingDesk Data

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.

Parameter	Type	Required	Description
`email`	string	Yes	The customer's email.
`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", or "Not sure".
`description`	string	—	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.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs submit_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 submit_order, this is the rule to start with:

submit_order Rate-limited

submit_order stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_order": {
      "limits": [
        {
          "counter": "submit_order_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FilingDesk Data, apply this rule, and every submit_order call is checked against it from then on.

FAQ

Questions about submit_order

What does the submit_order tool do? +

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. It is categorised as a Write tool in the FilingDesk Data MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does submit_order accept? +

submit_order accepts 8 parameters: email, phone, state, fullName, entityType, description, businessName, userConfirmed. Required: email, state, fullName, entityType, businessName, userConfirmed. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on submit_order? +

Register the FilingDesk Data MCP server in PolicyLayer and add a rule for submit_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.

What risk level is submit_order? +

submit_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_order? +

Yes. Add a rate_limit block to the submit_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.

How do I block submit_order completely? +

Set action: deny in the PolicyLayer policy for submit_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.

What MCP server provides submit_order? +

submit_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.

KEEP EXPLORING

More on FilingDesk Data, and thousands of servers like it.

This server

All 8 FilingDesk Data tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →