AI agents call timezone_convert to retrieve information from Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
toZone | string | — | Target timezone (optional) |
datetime | string | Yes | ISO datetime (e.g. 2026-06-04T12:00) |
fromZone | string | — | Source timezone (default: Asia/Shanghai) |
Parameters from the server's own tool schema.
This tool performs a pure computation/conversion of datetime values between time zones. It reads input data and returns a transformed result with no side effects, no data persistence, and no external operations.
From the tool's definition Convert datetime between time zones
Attacks that exploit this kind of access
Convert datetime between time zones. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
timezone_convert accepts 3 parameters: toZone, datetime, fromZone. Required: datetime. The full parameter table on this page comes from the server's own tool schema.
Register the Tools 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 Tools. 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 Tools MCP server (https://www.jiebang.site/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →