datetime_date_diff
Calculate the difference between two dates.
This record as markdown: /tools/creativelead-unclick/datetime-date-diff.md
What datetime_date_diff does on UnClick
AI agents call datetime_date_diff to retrieve information from UnClick 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 |
|---|---|---|---|
date1 | string | — | |
date2 | string | — |
Parameters from the server's own tool schema.
Why datetime_date_diff is rated Low
This is a utility function that performs arithmetic on date inputs to return a computed result. It reads/queries data (the two input dates) and returns a derived value without creating, modifying, deleting, or executing any operations with external consequences. The operation is deterministic and has no blast radius if misused.
From the tool's definition Tool name 'datetime_date_diff' and description 'Calculate the difference between two dates' indicate a pure calculation/retrieval operation with no side effects, data modification, execution, or financial impact.
Attacks that exploit this kind of access
The rule that runs datetime_date_diff safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datetime_date_diff, this is the rule to start with:
datetime_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 UnClick, apply this rule, and every datetime_date_diff call is checked against it from then on.
Questions about datetime_date_diff
Calculate the difference between two dates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
datetime_date_diff accepts 2 parameters: date1, date2. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for datetime_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 UnClick. Nothing to install.
datetime_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 datetime_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 datetime_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.
datetime_date_diff is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue