calendar.holidays.next
Next upcoming public holidays for a country — useful for scheduling, availability checks, business day calculations. No auth (Nager.Date)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/calendar.holidays.next.md
What calendar.holidays.next does on Apibase
AI agents call calendar.holidays.next to retrieve information from Apibase 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 |
|---|---|---|---|
country_code | string | Yes | ISO 3166-1 alpha-2 country code (e.g. "US", "FR") |
Parameters from the server's own tool schema.
Why calendar.holidays.next is rated Low
Tool queries holiday data with no side effects or modification capabilities.
From the tool's definition Next upcoming public holidays for a country — useful for scheduling, availability checks
Attacks that exploit this kind of access
The rule that runs calendar.holidays.next safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calendar.holidays.next, this is the rule to start with:
calendar.holidays.next 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 Apibase, apply this rule, and every calendar.holidays.next call is checked against it from then on.
Questions about calendar.holidays.next
Next upcoming public holidays for a country — useful for scheduling, availability checks, business day calculations. No auth (Nager.Date). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
calendar.holidays.next accepts 1 parameter: country_code. Required: country_code. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for calendar.holidays.next: 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 Apibase. Nothing to install.
calendar.holidays.next 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.holidays.next 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.holidays.next. 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.holidays.next is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue