// SCAN REPORT

FilingDesk Data

8 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 20 Aug 2026

2 can modify or destroy data

6 read-only

8 tools total

Community server · catalogue entry checked 20/08/2026 · full schemas captured for 7 of 8 tools

How to control FilingDesk Data ↓

TOOL MAP

What FilingDesk Data exposes to your agents

Read (6) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What FilingDesk Data costs in tokens

1,382 tokens of tool definitions, loaded on every request

0.7% of a 200k context window

278 heaviest tool: submit_order

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous FilingDesk Data tools

Execute · Medium preview_order Build an exact order summary WITHOUT submitting anything. No side effects. Validates the details, prices the order, and returns a confirmati Write · Medium 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 ca

2 of FilingDesk Data's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control FilingDesk Data

PolicyLayer is an MCP gateway — it sits between your AI agents and FilingDesk Data, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "submit_order": {
    "limits": [
      {
        "counter": "submit_order_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_llc_name": {
    "limits": [
      {
        "counter": "check_llc_name_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register FilingDesk Data — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FILINGDESK DATA →

Instant setup, no code required.

FULL CATALOGUE

All 8 FilingDesk Data tools

EXECUTE 1 tools

Execute preview_order Build an exact order summary WITHOUT submitting anything. No side effects. Validates the details, prices the o

WRITE 1 tools

Write submit_order Submit a real formation order to FilingDesk. THIS HAS A REAL-WORLD EFFECT: it creates an order and notifies a

READ 6 tools

Read check_llc_name Check a proposed business name against a state's live registry. REAL results for Wyoming and Delaware only; Fl Read compare_formation_options Factual tradeoffs to help someone decide WHERE to form or WHAT entity type to pick. Returns fixed comparative Read compare_llc_costs Rank states by what an LLC actually costs. Compares the one-time formation fee, the recurring state cost, and Read get_annual_report_deadline Work out when a state's annual report or franchise tax is next due, the amount owed, and the late penalty. Sta Read get_llc_fees Official LLC formation fee, recurring annual-report/franchise-tax cost, processing time, and known gotchas for Read list_filing_states What FilingDesk can do per state: which states it files in today with all-in pricing, which states have real n

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about FilingDesk Data

How do I prevent bulk modifications through FilingDesk Data? +

The FilingDesk Data server has 1 write tools including submit_order. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach FilingDesk Data.

How many tools does the FilingDesk Data MCP server expose? +

8 tools across 3 categories: Execute, Read, Write. 6 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on FilingDesk Data? +

Register the FilingDesk Data MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every FilingDesk Data tool call.

Deterministic rules across all 8 FilingDesk Data tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FILINGDESK DATA →

Instant setup, no code required.

8 FilingDesk Data tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from FilingDesk Data's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →