calendar.business-days
Holiday-aware business-day calculator for 200+ countries — the ground-truth answer for payment terms, SLA deadlines, and delivery dates instead of guessing holidays. Three modes: start+addDays shifts a date by N business days (signed); start+end counts business days between two dates (exclusive o...
This record as markdown: /tools/io-github-2s-io-mcp/calendar.business-days.md
What calendar.business-days does on Mcp
AI agents call calendar.business-days to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why calendar.business-days is rated Low
This tool purely computes and returns date/calendar information based on inputs. It performs no writes, executions, deletions, or financial transactions. It queries holiday data and calculates business days, which is a read-only operation. Despite being on a pay-per-call server, the tool itself does not move money — the billing is a server-level concern, not a tool action.
From the tool's definition 'business-day calculator', 'shifts a date by N business days', 'counts business days between two dates', 'checks one date' — all read/query/computation operations with no side effects
Attacks that exploit this kind of access
The rule that runs calendar.business-days safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calendar.business-days, this is the rule to start with:
calendar.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 Mcp, apply this rule, and every calendar.business-days call is checked against it from then on.
Questions about calendar.business-days
Holiday-aware business-day calculator for 200+ countries — the ground-truth answer for payment terms, SLA deadlines, and delivery dates instead of guessing holidays. Three modes: start+addDays shifts a date by N business days (signed); start+end counts business days between two dates (exclusive of start, inclusive of end); start alone checks one date (business day? which holiday? next/previous business day). Custom weekends supported (e.g. fri,sat for the Gulf). Skipped holidays are itemized. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for calendar.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 Mcp. Nothing to install.
calendar.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 calendar.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 calendar.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.
calendar.business-days is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue