Get active weather alerts, watches, warnings, and advisories for a location (US only). Use this for safety-critical weather information when asked about "any alerts?", "weather warnings?", "is it safe?", "dangerous weather?", or "weather watches?". Returns severity, urgency, certainty, effective/...
AI agents call get_alerts to retrieve information from Weather Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
latitude | number | Yes | Latitude of the location (-90 to 90) |
longitude | number | Yes | Longitude of the location (-180 to 180) |
active_only | boolean | — | Whether to show only active alerts (default: true) |
Parameters from the server's own tool schema.
This tool queries and returns weather alert information from NOAA/Open-Meteo APIs without any side effects. It is purely informational and read-only. The data returned is static weather information pulled from public APIs. No data is created, modified, deleted, or used to trigger external actions.
From the tool's definition Tool description explicitly states it retrieves "active weather alerts, watches, warnings, and advisories" and returns metadata (severity, urgency, certainty, times, affected areas). No modification, deletion, or execution of external operations is performed.
Attacks that exploit this kind of access
Get active weather alerts, watches, warnings, and advisories for a location (US only). Use this for safety-critical weather information when asked about "any alerts?", "weather warnings?", "is it safe?", "dangerous weather?", or "weather watches?". Returns severity, urgency, certainty, effective/expiration times, and affected areas. For forecast data, use get_forecast instead. If this tool returns an error, check the error message for status page links and consider using check_service_status to verify API availability. It is categorised as a Read tool in the Weather Data MCP Server MCP Server, which means it retrieves data without modifying state.
get_alerts accepts 3 parameters: latitude, longitude, active_only. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Weather Data MCP Server MCP server in PolicyLayer and add a rule for get_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 Weather Data MCP Server. Nothing to install.
get_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 get_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 get_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.
get_alerts is provided by the Weather Data MCP Server MCP server (@dangahagan/weather-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →