datetime_current_time
Get the current date and time, optionally in a specific timezone.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/datetime-current-time.md
What datetime_current_time does on UnClick
AI agents call datetime_current_time 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 |
|---|---|---|---|
format | string | — | |
timezone | string | — |
Parameters from the server's own tool schema.
Why datetime_current_time is rated Low
This tool only retrieves information (current date/time); it performs no modifications, deletions, executions, or financial operations. It is a pure read operation with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'datetime_current_time' and description 'Get the current date and time, optionally in a specific timezone' indicate a simple query operation that retrieves time data without side effects.
Attacks that exploit this kind of access
The rule that runs datetime_current_time 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_current_time, this is the rule to start with:
datetime_current_time 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_current_time call is checked against it from then on.
Questions about datetime_current_time
Get the current date and time, optionally in a specific timezone. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
datetime_current_time accepts 2 parameters: format, timezone. 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_current_time: 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_current_time 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_current_time 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_current_time. 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_current_time 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue