add_hu_working_days
Use this when you need a deterministic Hungary working-day offset. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when hungary 2026 general Monday-Friday work schedule only (Labour Code section 97(2), NGM 1...
This record as markdown: /tools/com-tttkmbb-calcgrid/add-hu-working-days.md
What add_hu_working_days does on Calcgrid
AI agents use add_hu_working_days to create or update resources in Calcgrid, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Calcgrid environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
start_date | string | Yes | Gregorian start date in 2026-2026. |
working_days | integer | Yes | Signed offset; start date excluded for non-zero offsets. |
work_schedule | string | Yes | Required: confirm the general Monday-Friday work schedule under Labour Code 97(2). Do not use for shifts or institution-specific opening. |
Parameters from the server's own tool schema.
Why add_hu_working_days is rated Medium
An AI agent can call add_hu_working_days faster than any human can review: one bad instruction and it creates or modifies resources in Calcgrid by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_hu_working_days safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Calcgrid, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_hu_working_days, this is the rule to start with:
add_hu_working_days stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Calcgrid, apply this rule, and every add_hu_working_days call is checked against it from then on.
Questions about add_hu_working_days
Use this when you need a deterministic Hungary working-day offset. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when hungary 2026 general Monday-Friday work schedule only (Labour Code section 97(2), NGM 10/2025). Requires explicit work_schedule. Eleven statutory holidays and three paired transfers are included; three Saturdays are working. No shift, personal, bank, exchange, school, local-office opening or payroll schedule is inferred. No automatic substitute Monday. The annual decree expires 2027-01-01; later schedules require new evidence. What it computes: Adds or subtracts Hungary authority-scope working days in exact coverage. Requires an explicit general Monday-Friday work schedule; includes three working Saturdays and paired rest dates. Example user requests: Add or subtract Hungary working days around Working Saturday compensates August 21. | Add or subtract Hungary working days around Christmas Eve is transferred rest, not statutory holiday. | Add or subtract Hungary working days around Whit Monday. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"general_monday_friday"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, work_schedule, is_statutory_holiday, is_transferred_rest_day, is_makeup_working_day, transfer_pair, payroll_scope. Formula: working = published makeup day OR (weekday AND not statutory holiday AND not transferred rest) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/hungary-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/hungary-public-add-working-days.md. It is categorised as a Write tool in the Calcgrid MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_hu_working_days accepts 3 parameters: start_date, working_days, work_schedule. Required: start_date, working_days, work_schedule. The full parameter table on this page comes from the server's own tool schema.
Register the Calcgrid MCP server in PolicyLayer and add a rule for add_hu_working_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 Calcgrid. Nothing to install.
add_hu_working_days is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_hu_working_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 add_hu_working_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.
add_hu_working_days is provided by the Calcgrid MCP server (https://tttkmbb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Calcgrid, and thousands of servers like it.
This server
Across the catalogue