timezone_convert
Time Zone Converter — Convert an ISO datetime between IANA time zones with correct DST offsets.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/timezone-convert.md
What timezone_convert does on Gateway
AI agents call timezone_convert to retrieve information from Gateway 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 |
|---|---|---|---|
to_zone | string | Yes | Target IANA zone, e.g. Asia/Tokyo |
datetime | string | Yes | ISO 8601 datetime |
from_zone | string | — | Source IANA zone for naive input (default UTC) |
Parameters from the server's own tool schema.
Why timezone_convert is rated Low
This tool performs a pure computational conversion of a datetime value from one time zone to another. It reads input data and returns a result with no side effects, no data modification, and no external operations triggered.
From the tool's definition Convert an ISO datetime between IANA time zones with correct DST offsets
Attacks that exploit this kind of access
The rule that runs timezone_convert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For timezone_convert, this is the rule to start with:
timezone_convert 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 Gateway, apply this rule, and every timezone_convert call is checked against it from then on.
Questions about timezone_convert
Time Zone Converter — Convert an ISO datetime between IANA time zones with correct DST offsets. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
timezone_convert accepts 3 parameters: to_zone, datetime, from_zone. Required: to_zone, datetime. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for timezone_convert: 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 Gateway. Nothing to install.
timezone_convert 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 timezone_convert 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 timezone_convert. 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.
timezone_convert is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue