get_weather_forecast_nws
Return a bounded US weather forecast for latitude/longitude through the public National Weather Service API. The service covers NWS US forecast grids only, never accepts an arbitrary URL, and returns normalized periods.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-weather-forecast-nws.md
What get_weather_forecast_nws does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_weather_forecast_nws to retrieve information from Delx Protocol — Agent Recovery & Continuity 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 |
|---|---|---|---|
periods | integer | — | Number of forecast periods to return. |
timeout | integer | — | Upstream timeout in seconds. |
latitude | number | Yes | Latitude in decimal degrees; NWS coverage is limited to the United States. |
longitude | number | Yes | Longitude in decimal degrees; NWS coverage is limited to the United States. |
Parameters from the server's own tool schema.
Why get_weather_forecast_nws is rated Low
The tool queries weather data from a public, read-only API. There are no destructive, financial, or execution capabilities involved. The bounded scope and explicit rejection of arbitrary URLs confirm it is a simple data retrieval operation with minimal risk of misuse.
From the tool's definition Tool description explicitly states it 'Return[s] a bounded US weather forecast' and 'returns normalized periods' — pure data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_weather_forecast_nws safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_weather_forecast_nws, this is the rule to start with:
get_weather_forecast_nws 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 Delx Protocol — Agent Recovery & Continuity, apply this rule, and every get_weather_forecast_nws call is checked against it from then on.
Questions about get_weather_forecast_nws
Return a bounded US weather forecast for latitude/longitude through the public National Weather Service API. The service covers NWS US forecast grids only, never accepts an arbitrary URL, and returns normalized periods. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
get_weather_forecast_nws accepts 4 parameters: periods, timeout, latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for get_weather_forecast_nws: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
get_weather_forecast_nws 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_forecast_nws 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_forecast_nws. 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_forecast_nws is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue