This record as markdown: /tools/creativelead-unclick/datetime-add-to-date.md
What datetime_add_to_date does on UnClick
AI agents call datetime_add_to_date as a supporting operation in UnClick workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | |
days | number | — | |
hours | number | — | |
years | number | — | |
months | number | — | |
minutes | number | — |
Parameters from the server's own tool schema.
Why datetime_add_to_date is rated Low
This tool performs a pure date arithmetic computation — adding a duration to a date. It has no side effects, does not retrieve external data, does not modify any system state, and involves no financial operations. It is a local calculation utility, making it genuinely 'Other'.
From the tool's definition Add a duration to a date
Attacks that exploit this kind of access
The rule that runs datetime_add_to_date 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_add_to_date, this is the rule to start with:
datetime_add_to_date gets a rate cap, and 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_add_to_date call is checked against it from then on.
Questions about datetime_add_to_date
Add a duration to a date. It is categorised as a Other tool in the UnClick MCP Server, which means it performs auxiliary operations.
datetime_add_to_date accepts 6 parameters: date, days, hours, years, months, minutes. 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_add_to_date: 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_add_to_date is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the datetime_add_to_date 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_add_to_date. 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_add_to_date 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