add_pe_working_days
Use this when you need a deterministic Peru 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 choose calendar_scope and workweek explicitly. National holidays and public-sector compens...
This record as markdown: /tools/com-tttkmbb-calcgrid/add-pe-working-days.md
What add_pe_working_days does on Calcgrid
AI agents use add_pe_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 |
|---|---|---|---|
workweek | integer | Yes | Required declared baseline: 5 = Saturday-Sunday rest, 6 = Sunday rest. Confirm the applicable roster. |
start_date | string | Yes | Gregorian start date in 2026-2026. |
working_days | integer | Yes | Signed offset; start date excluded for non-zero offsets. |
calendar_scope | string | Yes | Required: national_statutory uses 16 national holidays; public_sector also applies the two published compensable days. Neither is a tax or individual employee r |
Parameters from the server's own tool schema.
Why add_pe_working_days is rated Medium
An AI agent can call add_pe_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_pe_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_pe_working_days, this is the rule to start with:
add_pe_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_pe_working_days call is checked against it from then on.
Questions about add_pe_working_days
Use this when you need a deterministic Peru 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 choose calendar_scope and workweek explicitly. National holidays and public-sector compensable days have different applicability. This is a declared five-day (Saturday-Sunday rest) or six-day (Sunday rest) planning calendar, not proof of an individual's roster. Essential services, private-employer adoption, compensating shifts, regional holidays, banking, school, tax and procedural deadline calendars require separate evidence. The two compensable public-sector days remain working days for tax purposes. Later decrees require a new snapshot; dates beyond 2026 are unsupported. What it computes: Adds or subtracts Peru authority-scope working days in exact coverage. Required calendar_scope and workweek distinguish national holidays from compensable public-sector days and five/six-day rosters. Example user requests: Peru: National layer skips independence holidays. | Peru: Public-sector bridge changes deadline. Inputs: start_date (date); working_days (integer); calendar_scope (enum); workweek (integer). Complete JSON argument examples: {"start_date":"2026-07-24","working_days":1,"calendar_scope":"national_statutory","workweek":5} | {"start_date":"2026-07-24","working_days":1,"calendar_scope":"public_sector","workweek":5} 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, calendar_selection, workweek, compensable_day_details. Formula: working day = outside selected weekly rest and selected holiday layer Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/peru-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/peru-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_pe_working_days accepts 4 parameters: workweek, start_date, working_days, calendar_scope. Required: workweek, start_date, working_days, calendar_scope. 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_pe_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_pe_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_pe_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_pe_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_pe_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