getSalesTaxFiling
PREMIUM ONLY - Business tier and above; requests below that return an error. Filing frequencies and due dates by US state. Calendars are GENERATED from each state's published rules, so all state due dates stay correct across years. Handles what a naive 'due on the 20th' model gets wrong: due days...
This record as markdown: /tools/com-api-ninjas-mcp/getsalestaxfiling.md
What getSalesTaxFiling does on API Ninjas
AI agents call getSalesTaxFiling to retrieve information from API Ninjas 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 |
|---|---|---|---|
year | integer | — | Four-digit calendar year for the generated calendar. Defaults to the current year. |
state | string | — | Two-letter US state code or full state name (e.g. TX or Texas). Omit for all jurisdictions. |
frequency | string | — | Filing frequency tier, e.g. monthly, quarterly, semiannual, annual, monthly_accelerated. Returns the generated calendar for that tier. |
annual_liability | number | — | Annual sales tax liability in US dollars. Returns the frequency the state would assign, or 'indeterminate' where the state publishes no computable threshold. |
Parameters from the server's own tool schema.
Why getSalesTaxFiling is rated Low
Even though getSalesTaxFiling 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 getSalesTaxFiling safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getSalesTaxFiling, this is the rule to start with:
getSalesTaxFiling 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 API Ninjas, apply this rule, and every getSalesTaxFiling call is checked against it from then on.
Questions about getSalesTaxFiling
PREMIUM ONLY - Business tier and above; requests below that return an error. Filing frequencies and due dates by US state. Calendars are GENERATED from each state's published rules, so all state due dates stay correct across years. Handles what a naive 'due on the 20th' model gets wrong: due days ranging from the 15th (Maine) to the last day of the month (California); New York's quarters ending Feb/May/Aug/Nov; weekend and holiday rollover against federal, state or both calendars, flagged with due_date_adjusted and preserving statutory_due_date; electronic payments that must be INITIATED a business day early (Florida); and prepayment regimes in the four distinct placements states actually use. Supply annual_liability to have the state's own ladder assign a frequency. Where a state grants frequency by written approval or departmental notice rather than by a published dollar threshold, the response is 'indeterminate' rather than a guess. Each jurisdiction carries coverage_level, and any field the state does not publish is listed in unpublished with an unpublished_reason. State-level filing regimes only; home-rule localities that file separately are out of scope. This is reference data, not tax advice. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getSalesTaxFiling accepts 4 parameters: year, state, frequency, annual_liability. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getSalesTaxFiling: 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 API Ninjas. Nothing to install.
getSalesTaxFiling 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 getSalesTaxFiling 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 getSalesTaxFiling. 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.
getSalesTaxFiling is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue