count_or_add_business_days
utilpeek: Count business days between two dates or add working days, skipping public holidays. For the holiday list use get_public_holidays. Returns the business days between two dates (mode count; both ends included by default, like NETWORKDAYS) or the date N business days after or before a date...
This record as markdown: /tools/dev-tanod-tanod/count-or-add-business-days.md
What count_or_add_business_days does on Tanod
AI agents call count_or_add_business_days to retrieve information from Tanod 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 |
|---|---|---|---|
end | object | — | count only: end date, YYYY-MM-DD, at most 20 years from start (before start gives a negative count). |
days | object | — | add only: business days to add (negative subtracts). The start date is never counted (like Excel WORKDAY); 0 returns start. |
mode | string | Yes | count: business days between start and end; add: the date `days` business days after (or before) start. |
start | string | Yes | Start date, YYYY-MM-DD (1900-01-01..2199-12-31). |
country | object | — | Optional ISO 3166-1 alpha-2 country whose public holidays are not business days (the /v1/holidays data; dates in 1990-2100). |
weekend | array | — | Weekday names that are not business days (default ["sat", "sun"]; e.g. ["fri", "sat"]; [] for none). |
include_end | object | — | count only: count the end date (default true; both true is Excel NETWORKDAYS, include_end false the half-open [start, end) of numpy.busday_count). |
subdivision | object | — | Optional subdivision code or name for that country (e.g. CA or California for US). |
include_start | object | — | count only: count the start date (default true). |
Parameters from the server's own tool schema.
Why count_or_add_business_days is rated Low
Even though count_or_add_business_days 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 count_or_add_business_days safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For count_or_add_business_days, this is the rule to start with:
count_or_add_business_days 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 Tanod, apply this rule, and every count_or_add_business_days call is checked against it from then on.
Questions about count_or_add_business_days
utilpeek: Count business days between two dates or add working days, skipping public holidays. For the holiday list use get_public_holidays. Returns the business days between two dates (mode count; both ends included by default, like NETWORKDAYS) or the date N business days after or before a date (mode add, like WORKDAY), skipping weekends (configurable) and, with a country, its public holidays; plus the holidays skipped. Input: mode, start, for count end and optional include_start / include_end, for add days, optional weekend, country and subdivision. Ranges up to 20 years; with a country, dates in 1990-2100. Bad input is a 422 (not charged). Holiday rules are modelled by a library: confirm with an official source for legal or payroll use. Typically under 0.2 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/business-days-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
count_or_add_business_days accepts 9 parameters: end, days, mode, start, country, weekend, include_end, subdivision, include_start. Required: mode, start. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for count_or_add_business_days: 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 Tanod. Nothing to install.
count_or_add_business_days 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 count_or_add_business_days 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 count_or_add_business_days. 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.
count_or_add_business_days is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue