nws_active_alerts
Currently-active National Weather Service alerts (tornado, flood, severe thunderstorm, winter, heat, fire) for a point, state, or NWS zone.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nws-active-alerts.md
What nws_active_alerts does on Livedatalink
AI agents call nws_active_alerts to retrieve information from Livedatalink 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 | — | |
lon | number | — | |
zone | string | — | NWS zone id, e.g. 'TXZ123'. |
state | string | — | Two-letter state code (e.g. 'TX'). |
location | string | — | Address, zip, or city. Will be geocoded to a point. |
Parameters from the server's own tool schema.
Why nws_active_alerts is rated Low
Even though nws_active_alerts 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 nws_active_alerts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nws_active_alerts, this is the rule to start with:
nws_active_alerts 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 Livedatalink, apply this rule, and every nws_active_alerts call is checked against it from then on.
Questions about nws_active_alerts
Currently-active National Weather Service alerts (tornado, flood, severe thunderstorm, winter, heat, fire) for a point, state, or NWS zone. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
nws_active_alerts accepts 5 parameters: lat, lon, zone, state, location. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for nws_active_alerts: 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 Livedatalink. Nothing to install.
nws_active_alerts 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 nws_active_alerts 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 nws_active_alerts. 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.
nws_active_alerts is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue