weather.alerts.active
Active severe weather alerts for the US — tornado warnings, flood watches, heat advisories, winter storms. Filter by state, severity, event type. US Government open data, unlimited, no auth (NWS/NOAA)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/weather.alerts.active.md
What weather.alerts.active does on Apibase
AI agents call weather.alerts.active 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 |
|---|---|---|---|
area | string | — | US state code (e.g. "CA", "TX", "NY") or marine zone |
event | string | — | Event type filter (e.g. "Tornado Warning", "Flood Watch", "Heat Advisory") |
limit | integer | — | Max alerts to return (default 10, max 50) |
urgency | string | — | Urgency filter |
severity | string | — | Alert severity filter |
Parameters from the server's own tool schema.
Why weather.alerts.active is rated Low
Queries public weather data with no side effects or modification capability.
From the tool's definition retrieves severe weather alerts, filter by state/severity/type, no auth, open data
Attacks that exploit this kind of access
The rule that runs weather.alerts.active 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 weather.alerts.active, this is the rule to start with:
weather.alerts.active 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 weather.alerts.active call is checked against it from then on.
Questions about weather.alerts.active
Active severe weather alerts for the US — tornado warnings, flood watches, heat advisories, winter storms. Filter by state, severity, event type. US Government open data, unlimited, no auth (NWS/NOAA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
weather.alerts.active accepts 5 parameters: area, event, limit, urgency, severity. 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 weather.alerts.active: 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.
weather.alerts.active 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.alerts.active 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.alerts.active. 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.alerts.active 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