Get weather forecast for a location.
AI agents call get_forecast to retrieve information from Weather Alerts MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool. It queries the National Weather Service API to obtain forecast information and returns it to the user. There are no side effects, no data modification, no code execution, and no destructive operations. The lowest blast radius applies: misuse simply returns weather data that is already public.
From the tool's definition Tool description states 'Get weather forecast for a location' — a retrieval operation that fetches data with no modification, deletion, or execution of external code. It queries weather data and returns formatted results.
Attacks that exploit this kind of access
Get weather forecast for a location. It is categorised as a Read tool in the Weather Alerts MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather Alerts MCP Server MCP server in PolicyLayer and add a rule for get_forecast: 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 Alerts MCP Server. Nothing to install.
get_forecast 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_forecast 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_forecast. 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_forecast is provided by the Weather Alerts MCP Server MCP server (nehasj99/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 →