Get the most recent weather observation for a location (US only). Use this for current weather or when asking about "today's weather", "right now", or recent conditions without a specific historical date range. Returns the latest observation from the nearest weather station. Optionally includes f...
AI agents call get_current_conditions 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) |
include_normals | boolean | — | Include climate normals (30-year averages) for comparison with current conditions (default: false). Shows normal high/low temperatures and precipitation, with d |
include_fire_weather | boolean | — | Include fire weather indices (Haines Index, Grassland Fire Danger, Red Flag Threat) in the response (default: false, US only) |
Parameters from the server's own tool schema.
This tool performs a straightforward data retrieval operation querying current weather conditions from NOAA and Open-Meteo APIs. It has no side effects, cannot modify or delete data, and poses minimal risk even if misused by an AI agent. The worst outcome would be excessive API calls or irrelevant weather queries.
From the tool's definition Tool retrieves 'the most recent weather observation' and 'returns the latest observation from the nearest weather station' with no modification capability mentioned. No deletion, creation, code execution, or financial operations described.
Attacks that exploit this kind of access
Get the most recent weather observation for a location (US only). Use this for current weather or when asking about "today's weather", "right now", or recent conditions without a specific historical date range. Returns the latest observation from the nearest weather station. Optionally includes fire weather indices (Haines Index, Grassland Fire Danger, Red Flag Threat) when requested. For specific past dates or date ranges, use get_historical_weather 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_current_conditions accepts 4 parameters: latitude, longitude, include_normals, include_fire_weather. 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_current_conditions: 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_current_conditions 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_current_conditions 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_current_conditions. 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_current_conditions 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 →