convert_timezone · Temporal Cortex Calendar MCP

WHAT IT DOES

What convert_timezone does on Temporal Cortex Calendar MCP

AI agents use convert_timezone to create or update resources in Temporal Cortex Calendar MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Temporal Cortex Calendar MCP environment.

PARAMETERS

Parameter	Type	Required	Description
`datetime`	string	Yes	RFC 3339 datetime string to convert.
`target_timezone`	string	Yes	Target IANA timezone.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why convert_timezone needs a policy

An AI agent can call convert_timezone faster than any human can review — one bad instruction and it creates or modifies resources in Temporal Cortex Calendar MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_timezone Rate-limited

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": {
    "convert_timezone": {
      "limits": [
        {
          "counter": "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 Temporal Cortex Calendar MCP, so you can run agents against it safely.

FAQ

Questions about convert_timezone

What does the convert_timezone tool do? +

Convert a datetime to a different timezone. It is categorised as a Write tool in the Temporal Cortex Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does convert_timezone accept? +

convert_timezone accepts 2 parameters: datetime, target_timezone. Required: datetime, target_timezone. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on convert_timezone? +

Register the Temporal Cortex Calendar MCP server in PolicyLayer and add a rule for 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 Temporal Cortex Calendar MCP. Nothing to install.

What risk level is convert_timezone? +

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

Can I rate-limit convert_timezone? +

Yes. Add a rate_limit block to the 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 convert_timezone completely? +

Set action: deny in the PolicyLayer policy for 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 convert_timezone? +

convert_timezone is provided by the Temporal Cortex Calendar MCP server (temporal-cortex/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.