Get the current time and zone info at any point (geographic coordinates). Output includes includes the standard UTC offset, special offset currently in effect (typically but not always Daylight Saving Time), IANA TZID, and the current timestamp in RFC 28222 format.
AI agents call time-and-zone-info to retrieve information from Stadia Maps Location API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves timezone and time information based on geographic coordinates. It has no side effects, does not modify any data, does not execute code or commands, does not delete anything, and does not move money. It is a straightforward read operation with minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] the current time and zone info' - purely a retrieval operation with no modification, deletion, or execution capabilities. Returns UTC offset, timezone identifier, and timestamp.
Documented attack patterns abuse exactly the kind of access time-and-zone-info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stadia Maps Location API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for time-and-zone-info:
{
"version": "1",
"default": "deny",
"tools": {
"time-and-zone-info": {}
}
}time-and-zone-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 the current time and zone info at any point (geographic coordinates). Output includes includes the standard UTC offset, special offset currently in effect (typically but not always Daylight Saving Time), IANA TZID, and the current timestamp in RFC 28222 format. It is categorised as a Read tool in the Stadia Maps Location API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stadia Maps Location API MCP Server MCP server in PolicyLayer and add a rule for time-and-zone-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 Stadia Maps Location API MCP Server. Nothing to install.
time-and-zone-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 time-and-zone-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 time-and-zone-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.
time-and-zone-info is provided by the Stadia Maps Location API MCP Server MCP server (stadiamaps/stadiamaps-mcp-server-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stadia Maps Location API 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.
6 Stadia Maps Location API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.