lookup_weather
Retrieves comprehensive weather data including current conditions, hourly, and daily forecasts. Specific Data Available: Temperature (Current, Feels Like, Max/Min, Heat Index), Wind (Speed, Gusts, Direction), Celestial Events (Sunrise/Sunset, Moon Phase), Precipitation (Type, Probability, Quantit...
This record as markdown: /tools/com-googleapis-mapstools-mcp/lookup-weather.md
What lookup_weather does on Mcp
AI agents call lookup_weather to retrieve information from Mcp 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 |
|---|---|---|---|
date | object | — | Optional. The date of the required weather information. Note: This date is relative to the local timezone of the location specified in the location field. The d |
hour | integer | — | Optional. The hour of the requested weather information, in 24-hour format (0-23). This value is relative to the local timezone of the location specified in the |
location | object | Yes | Required. The location to get the weather conditions for. |
unitsSystem | string | — | Optional. The units system to use for the returned weather conditions. If not provided, the returned weather conditions will be in the metric system (default = |
Parameters from the server's own tool schema.
Why lookup_weather is rated Low
This tool performs pure data retrieval without side effects. It queries weather information and returns forecasts and current conditions. There is no capability to modify data, execute code, delete resources, or conduct financial transactions. The severity is low because misuse (e.g., requesting weather for many locations) causes minimal harm—only data queries with no destructive or systemic impact.
From the tool's definition Tool description explicitly states it 'Retrieves comprehensive weather data' including temperature, wind, precipitation, atmospheric conditions, and location address.
Attacks that exploit this kind of access
The rule that runs lookup_weather safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lookup_weather, this is the rule to start with:
lookup_weather 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 Mcp, apply this rule, and every lookup_weather call is checked against it from then on.
Questions about lookup_weather
Retrieves comprehensive weather data including current conditions, hourly, and daily forecasts. Specific Data Available: Temperature (Current, Feels Like, Max/Min, Heat Index), Wind (Speed, Gusts, Direction), Celestial Events (Sunrise/Sunset, Moon Phase), Precipitation (Type, Probability, Quantity/QPF), Atmospheric Conditions (UV Index, Humidity, Cloud Cover, Thunderstorm Probability), and Geocoded Location Address. Location & Location Rules (CRITICAL): The location for which weather data is requested is specified using the location field. This field is a 'oneof' structure, meaning you MUST provide a value for ONLY ONE of the three location sub-fields below to ensure an accurate weather data lookup. 1. Geographic Coordinates (lat_lng) * Use it when you are provided with exact lat/lng coordinates. * Example: {"location": {"lat_lng": {"latitude": 34.0522, "longitude": -118.2437}}} // Los Angeles 2. Place ID (place_id) * An unambiguous string identifier (Google Maps Place ID). * The place_id can be fetched from the search_places tool. * Example: {"location": {"place_id": "ChIJLU7jZClu5kcR4PcOOO6p3I0"}} // Eiffel Tower 3. Address String (address) * A free-form string that requires specificity for geocoding. * City & Region: Always include region/country (e.g., "London, UK", not "London"). * Street Address: Provide the full address (e.g., "1600 Pennsylvania Ave NW, Washington, DC"). * Postal/Zip Codes: MUST be accompanied by a country name (e.g., "90210, USA", NOT "90210"). * Example: {"location": {"address": "1600 Pennsylvania Ave NW, Washington, DC"}} Usage Modes: * Current Weather: Provide location only. Do not specify date and hour. * Hourly Forecast: Provide location, date, and hour (0-23). Use for specific times (e.g., "at 5 PM") or terms like "next few hours" or "later today". If the user specifies minute, round down to the nearest hour. Hourly forecast beyond 120 hours from now is not supported. Historical hourly weather is supported up to 24 hours in the past. * Daily Forecast: Provide location and date. Do not specify hour. Use for general day requests (e.g., "weather for tomorrow", "weather on Friday", "weather on 12/25"). If today's date is not in the context, you should clarify it with the user. Daily forecast beyond 10 days including today is not supported. Historical weather is not supported. Parameter Constraints: * Timezones: All date and hour inputs must be relative to the location's local time zone, not the user's time zone. * Date Format: Inputs must be separated into {year, month, day} integers. * Units: Defaults to METRIC. Set units_system to IMPERIAL for Fahrenheit/Miles if the user implies US standards or explicitly requests it. * The grounded output must be attributed to the source using the information from the attribution field when available. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
lookup_weather accepts 4 parameters: date, hour, location, unitsSystem. Required: location. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for lookup_weather: 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 Mcp. Nothing to install.
lookup_weather 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 lookup_weather 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 lookup_weather. 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.
lookup_weather is provided by the MCP server (https://mapstools.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue