date_add
Date Arithmetic (add duration) — Add years/months/weeks/days/hours to an ISO date; month math clamps to end-of-month.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/date-add.md
What date_add does on Gateway
AI agents call date_add to retrieve information from Gateway 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 |
|---|---|---|---|
date | string | Yes | ISO date YYYY-MM-DD or full datetime |
days | integer | — | Days to add (may be negative) |
hours | integer | — | Hours to add (may be negative) |
weeks | integer | — | Weeks to add (may be negative) |
years | integer | — | Years to add (may be negative) |
months | integer | — | Months to add (may be negative) |
minutes | integer | — | Minutes to add (may be negative) |
seconds | integer | — | Seconds to add (may be negative) |
Parameters from the server's own tool schema.
Why date_add is rated Low
This tool performs a pure calculation on date inputs and returns a computed result. It has no side effects, does not write or delete any data, and does not trigger external operations. It is a stateless arithmetic utility.
From the tool's definition Date Arithmetic (add duration) — Add years/months/weeks/days/hours to an ISO date; month math clamps to end-of-month.
Attacks that exploit this kind of access
The rule that runs date_add safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For date_add, this is the rule to start with:
date_add 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 Gateway, apply this rule, and every date_add call is checked against it from then on.
Questions about date_add
Date Arithmetic (add duration) — Add years/months/weeks/days/hours to an ISO date; month math clamps to end-of-month. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
date_add accepts 8 parameters: date, days, hours, weeks, years, months, minutes, seconds. Required: date. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for date_add: 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 Gateway. Nothing to install.
date_add 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 date_add 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 date_add. 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.
date_add is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue