weather.alerts.by_state
Active weather alerts for a specific US state — all warnings, watches, and advisories. Returns event, severity, urgency, description, area, timing (NWS/NOAA)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/weather.alerts.by-state.md
What weather.alerts.by_state does on Apibase
AI agents call weather.alerts.by_state 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 |
|---|---|---|---|
limit | integer | — | Max alerts (default 10, max 50) |
state | string | Yes | US state code (e.g. "CA", "FL", "TX") |
Parameters from the server's own tool schema.
Why weather.alerts.by_state is rated Low
Tool retrieves weather data with no side effects, modifications, or financial impact.
From the tool's definition retrieves active weather alerts, returns event, severity, urgency, description, area, timing
Attacks that exploit this kind of access
The rule that runs weather.alerts.by_state 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.by_state, this is the rule to start with:
weather.alerts.by_state 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.by_state call is checked against it from then on.
Questions about weather.alerts.by_state
Active weather alerts for a specific US state — all warnings, watches, and advisories. Returns event, severity, urgency, description, area, timing (NWS/NOAA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
weather.alerts.by_state accepts 2 parameters: limit, state. Required: state. 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.by_state: 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.by_state 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.by_state 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.by_state. 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.by_state 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