date_diff
Date Difference Calculator — Days, weeks, months and business days between two ISO dates.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/date-diff.md
What date_diff does on Gateway
AI agents call date_diff 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 |
|---|---|---|---|
end_date | string | Yes | End date, ISO 'YYYY-MM-DD' |
start_date | string | Yes | Start date, ISO 'YYYY-MM-DD' |
Parameters from the server's own tool schema.
Why date_diff is rated Low
The tool takes two ISO date inputs and returns calculated differences in various time units. It performs arithmetic calculations on date values without creating, modifying, deleting, or executing external operations. No data is persisted, modified, or at risk of being irreversibly lost. This is a safe read-only calculator utility.
From the tool's definition Tool name 'date_diff' and description explicitly states it 'calculates... Days, weeks, months and business days between two ISO dates.' This is a pure computation/query operation with no side effects on data.
Attacks that exploit this kind of access
The rule that runs date_diff 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_diff, this is the rule to start with:
date_diff 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_diff call is checked against it from then on.
Questions about date_diff
Date Difference Calculator — Days, weeks, months and business days between two ISO dates. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
date_diff accepts 2 parameters: end_date, start_date. Required: end_date, start_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_diff: 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_diff 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_diff 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_diff. 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_diff 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