Get current time in specified timezone.
AI agents call get_current_datetime 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'). Use UTC timezone if no timezone provided by the user. |
Parameters from the server's own tool schema.
This tool only retrieves and returns time data for a specified timezone. It performs no write, destructive, financial, or execution operations. The retrieval of datetime information has minimal blast radius—even if misused by an agent, providing incorrect timezone information cannot cause harm. It is a straightforward Read operation.
From the tool's definition Tool name 'get_current_datetime' and description 'Get current time in specified timezone' indicate a pure query operation that retrieves time information without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_current_datetime 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_current_datetime:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_datetime": {}
}
}get_current_datetime 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 current time in specified timezone. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
get_current_datetime 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_current_datetime: 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_current_datetime 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_current_datetime 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_current_datetime. 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_current_datetime 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.