Convert time from one timezone to another.
AI agents call convert_time as a supporting operation in Weather MCP Server workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
to_timezone | string | — | Target timezone (IANA timezone name) |
datetime_str | string | — | DateTime string in ISO format (e.g., '2024-01-15T14:30:00') or 'now' for current time |
from_timezone | string | — | Source timezone (IANA timezone name) |
Parameters from the server's own tool schema.
This tool performs a pure in-memory timezone conversion calculation with no side effects, no data retrieval from external systems, no writes, and no execution of commands. It is a stateless utility function that transforms a time value between timezones.
From the tool's definition Convert time from one timezone to another
Documented attack patterns abuse exactly the kind of access convert_time gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weather MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_time:
{
"version": "1",
"default": "deny",
"tools": {
"convert_time": {
"limits": [
{
"counter": "convert_time_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}convert_time gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Convert time from one timezone to another. It is categorised as a Other tool in the Weather MCP Server MCP Server, which means it performs auxiliary operations.
convert_time accepts 3 parameters: to_timezone, datetime_str, from_timezone. The full parameter table on this page comes from the server's own tool schema.
Register the Weather MCP Server MCP server in PolicyLayer and add a rule for convert_time: 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 Weather MCP Server. Nothing to install.
convert_time is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the convert_time 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 convert_time. 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.
convert_time is provided by the Weather MCP Server MCP server (isdaniel/mcp_weather_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weather MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Weather MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.