AI agents call datetime_date_diff to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date1 | string | Yes | |
date2 | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves or computes information (date difference) without creating, modifying, deleting, or executing external operations. It is a stateless mathematical operation with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'datetime_date_diff' and description 'Calculate the difference between two dates' indicate a pure calculation/query operation with no data modification, deletion, or external side effects.
Attacks that exploit this kind of access
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. Required: 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 (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →