datetime_convert_timezone · UnClick MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required
`datetime`	string	Yes
`to_timezone`	string	Yes
`from_timezone`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why datetime_convert_timezone needs a policy

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

Recommended rule Ready

Verdict

datetime_convert_timezone Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "datetime_convert_timezone": {
      "limits": [
        {
          "counter": "datetime_convert_timezone_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UnClick, so you can run agents against it safely.

FAQ

Questions about datetime_convert_timezone

What does the datetime_convert_timezone tool do? +

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.

What parameters does datetime_convert_timezone accept? +

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.

How do I enforce a policy on datetime_convert_timezone? +

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.

What risk level is datetime_convert_timezone? +

datetime_convert_timezone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit datetime_convert_timezone? +

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.

How do I block datetime_convert_timezone completely? +

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.

What MCP server provides datetime_convert_timezone? +

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.