get_weather
weatherpeek: hourly weather forecast for a point or a city. For airport observations use get_metar. Input: either lat and lon together, or place alone, plus optional hours. place matches cities of 15,000+ people offline ("City" or "City, CC" with an ISO country code); no match is a 404 place_not_...
This record as markdown: /tools/dev-tanod-tanod/get-weather.md
What get_weather does on Tanod
AI agents call get_weather to retrieve information from Tanod 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 |
|---|---|---|---|
lat | object | — | Latitude (-90..90); give lat and lon together, or place. |
lon | object | — | Longitude (-180..180); give lat and lon together, or place. |
hours | integer | — | Hourly rows to return (1-48, default 24). |
place | object | — | City name, optionally "City, CC" with an ISO country code (cities with 15,000+ people); give place alone, or lat and lon. |
Parameters from the server's own tool schema.
Why get_weather is rated Low
Even though get_weather only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_weather safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_weather, this is the rule to start with:
get_weather 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 Tanod, apply this rule, and every get_weather call is checked against it from then on.
Questions about get_weather
weatherpeek: hourly weather forecast for a point or a city. For airport observations use get_metar. Input: either lat and lon together, or place alone, plus optional hours. place matches cities of 15,000+ people offline ("City" or "City, CC" with an ISO country code); no match is a 404 place_not_found (not charged). Upstream errors are a 5xx and are not charged. Typically 0.1-2 s. Price: USD 0.002. Free: 5 weather forecasts per IP per UTC day. Data: MET Norway and GeoNames, both CC BY 4.0; credit them when you show or republish it (see attribution). Forecasts are numerical weather model output and can be wrong: not for safety-critical decisions (aviation, marine, severe-weather warnings); use official services for those. Docs: https://tanod.dev/learn/weather-api-no-key.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
get_weather accepts 4 parameters: lat, lon, hours, place. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for get_weather: 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 Tanod. Nothing to install.
get_weather 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_weather 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_weather. 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_weather is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue