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. States that key the deadline to the formation anniversary or quarter need formationDate; without it the tool says so instead of guessing a date.
This record as markdown: /tools/com-filingdesk-data/get-annual-report-deadline.md
What get_annual_report_deadline does on FilingDesk Data
AI agents call get_annual_report_deadline to retrieve information from FilingDesk Data without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
state | string | Yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
formationDate | string | — | The LLC's formation date as ISO yyyy-mm-dd. Required for anniversary- and quarter-based states. |
Parameters from the server's own tool schema.
Why get_annual_report_deadline is rated Low
Even though get_annual_report_deadline only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_annual_report_deadline 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 get_annual_report_deadline, this is the rule to start with:
get_annual_report_deadline is read-only, so it stays allowed. 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 get_annual_report_deadline call is checked against it from then on.
Questions about 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. States that key the deadline to the formation anniversary or quarter need formationDate; without it the tool says so instead of guessing a date. It is categorised as a Read tool in the FilingDesk Data MCP Server, which means it retrieves data without modifying state.
get_annual_report_deadline accepts 2 parameters: state, formationDate. Required: state. 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 get_annual_report_deadline: 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.
get_annual_report_deadline is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_annual_report_deadline 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 get_annual_report_deadline. 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.
get_annual_report_deadline 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.
This server
Across the catalogue