geonames.place.timezone
Look up the timezone for any coordinates on Earth using the GeoNames database. Returns IANA timezone ID (e.g. "America/New_York", "Europe/London"), GMT offset, DST offset, raw (winter) offset, current local time, today's sunrise and sunset times (local), and the country at those coordinates. Usef...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geonames.place.timezone.md
What geonames.place.timezone does on Apibase
AI agents call geonames.place.timezone to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
language | string | — | ISO 639-1 language code for the country name in the response (e.g. "en", "de") |
latitude | number | Yes | Latitude of the location to look up (-90 to 90, e.g. 40.7128 for New York City) |
longitude | number | Yes | Longitude of the location to look up (-180 to 180, e.g. -74.0060 for New York City) |
Parameters from the server's own tool schema.
Why geonames.place.timezone is rated Low
Retrieves timezone and location data with no side effects or external state changes.
From the tool's definition Look up timezone for coordinates. Returns IANA timezone ID, GMT offset, sunrise/sunset times.
Attacks that exploit this kind of access
The rule that runs geonames.place.timezone safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geonames.place.timezone, this is the rule to start with:
geonames.place.timezone is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every geonames.place.timezone call is checked against it from then on.
Questions about geonames.place.timezone
Look up the timezone for any coordinates on Earth using the GeoNames database. Returns IANA timezone ID (e.g. "America/New_York", "Europe/London"), GMT offset, DST offset, raw (winter) offset, current local time, today's sunrise and sunset times (local), and the country at those coordinates. Useful for scheduling tasks across time zones, converting UTC timestamps, or annotating location data with timezone context. CC BY 4.0 open data, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geonames.place.timezone accepts 3 parameters: language, latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for geonames.place.timezone: 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 Apibase. Nothing to install.
geonames.place.timezone 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 geonames.place.timezone 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 geonames.place.timezone. 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.
geonames.place.timezone is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue