Get information about a specific timezone including current time and UTC offset.
AI agents call get_timezone_info to retrieve information from Weather MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
timezone_name | string | — | IANA timezone name (e.g., 'America/New_York', 'Europe/London') |
Parameters from the server's own tool schema.
This tool performs a simple data retrieval operation that queries timezone metadata and current time information. It has no side effects, does not modify data, execute code, or consume financial resources. The blast radius of misuse is minimal—an AI agent could only retrieve timezone data for many locations or repeatedly query the service, but cannot cause harm through the tool itself.
From the tool's definition Tool retrieves timezone information and current time (read-only queries). Description states it 'Get[s] information about a specific timezone' with no modification, deletion, or execution capabilities mentioned.
Documented attack patterns abuse exactly the kind of access get_timezone_info 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 get_timezone_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_timezone_info": {}
}
}get_timezone_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about a specific timezone including current time and UTC offset. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
get_timezone_info accepts 1 parameter: timezone_name. 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 get_timezone_info: 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.
get_timezone_info 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 get_timezone_info 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 get_timezone_info. 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.
get_timezone_info 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.