Get active weather alerts for a US state. Only covers the United States (powered by National Weather Service).
AI agents call get_alerts to retrieve information from Weather MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves weather alert information without creating, modifying, deleting, or executing any operations. It is a read-only information retrieval function with minimal risk—the worst outcome would be stale or incorrect alert data returned to the user. No financial, destructive, or execution-based actions are performed.
From the tool's definition Tool retrieves alert data ('Get active weather alerts') with no modification, creation, deletion, or external side effects. Powered by National Weather Service API for passive data retrieval only.
Attacks that exploit this kind of access
Get active weather alerts for a US state. Only covers the United States (powered by National Weather Service). It is categorised as a Read tool in the Weather MCP MCP Server, which means it retrieves data without modifying state.
Register the Weather 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 MCP. 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 MCP server (srewatkar/weather). 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 →