weather_nws
US weather from the National Weather Service for a latitude/longitude: 7-day (or hourly) forecast periods with temperature, precipitation chance, wind and text forecast, plus all active NWS watches, warnings and advisories for that point. US states, territories and coastal waters only. Price: $0....
This record as markdown: /tools/com-it-scorptech-x402/weather-nws.md
What weather_nws does on ScorpTech x402 API
AI agents call weather_nws to retrieve information from ScorpTech x402 API 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 | number | Yes | Latitude (-90..90), US location |
lon | number | Yes | Longitude (-180..180), US location |
units | string | — | us (F, mph; default) or si (C, km/h) |
hourly | boolean | — | true for the next 48 hourly periods instead of 14 day/night periods |
Parameters from the server's own tool schema.
Why weather_nws is rated Low
Even though weather_nws 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 weather_nws safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For weather_nws, this is the rule to start with:
weather_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 ScorpTech x402 API, apply this rule, and every weather_nws call is checked against it from then on.
Questions about weather_nws
US weather from the National Weather Service for a latitude/longitude: 7-day (or hourly) forecast periods with temperature, precipitation chance, wind and text forecast, plus all active NWS watches, warnings and advisories for that point. US states, territories and coastal waters only. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/weather-nws. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
weather_nws accepts 4 parameters: lat, lon, units, hourly. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for weather_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 ScorpTech x402 API. Nothing to install.
weather_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 weather_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 weather_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.
weather_nws is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue