datetime_convert_timezone
Convert a datetime from one timezone to another.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/datetime-convert-timezone.md
What datetime_convert_timezone does on UnClick
AI agents use datetime_convert_timezone to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
datetime | string | Yes | |
to_timezone | string | Yes | |
from_timezone | string | Yes |
Parameters from the server's own tool schema.
Why datetime_convert_timezone is rated Medium
An AI agent can call datetime_convert_timezone faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs datetime_convert_timezone 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_convert_timezone, this is the rule to start with:
datetime_convert_timezone stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_convert_timezone call is checked against it from then on.
Questions about datetime_convert_timezone
Convert a datetime from one timezone to another. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
datetime_convert_timezone accepts 3 parameters: datetime, to_timezone, from_timezone. Required: datetime, to_timezone, from_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_convert_timezone: 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_convert_timezone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the datetime_convert_timezone 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_convert_timezone. 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_convert_timezone 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