noaa.weather.hourly
Get hourly weather forecast (next 48 hours) for a US location by latitude/longitude. Returns temperature (°F), precipitation chance, wind speed/direction, and short conditions per hour. Powered by NOAA National Weather Service. US contiguous only.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/noaa.weather.hourly.md
What noaa.weather.hourly does on Apibase
AI agents call noaa.weather.hourly 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 |
|---|---|---|---|
latitude | number | Yes | Latitude in decimal degrees (US contiguous only: 24–50) |
longitude | number | Yes | Longitude in decimal degrees (US contiguous only: −125 to −66) |
Parameters from the server's own tool schema.
Why noaa.weather.hourly is rated Low
Retrieves weather data with no side effects or system modifications.
From the tool's definition Get hourly weather forecast, retrieves temperature, precipitation, wind data.
Attacks that exploit this kind of access
The rule that runs noaa.weather.hourly 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 noaa.weather.hourly, this is the rule to start with:
noaa.weather.hourly 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 noaa.weather.hourly call is checked against it from then on.
Questions about noaa.weather.hourly
Get hourly weather forecast (next 48 hours) for a US location by latitude/longitude. Returns temperature (°F), precipitation chance, wind speed/direction, and short conditions per hour. Powered by NOAA National Weather Service. US contiguous only. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
noaa.weather.hourly accepts 2 parameters: 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 noaa.weather.hourly: 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.
noaa.weather.hourly 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 noaa.weather.hourly 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 noaa.weather.hourly. 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.
noaa.weather.hourly 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