get_weather
Gets the current weather and a short daily forecast for a location. Pass a city name ('London', 'San Francisco', 'Tokyo,JP') or 'lat,lon' coordinates. Uses Open-Meteo — no API key required. Location must be provided (there is no device-location access).
This record as markdown: /tools/com-local-mcp-local-mcp/get-weather.md
What get_weather does on Local
AI agents call get_weather to retrieve information from Local 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 |
|---|---|---|---|
days | integer | — | Number of forecast days, 1-7 (default 3) |
location | string | Yes | City name (e.g. 'London', 'Buenos Aires', 'Tokyo,JP') or 'lat,lon' coordinates (e.g. '40.71,-74.01') |
Parameters from the server's own tool schema.
Why get_weather is rated Low
This tool retrieves weather data from Open-Meteo based on user-provided location parameters. It has no ability to modify, delete, execute arbitrary operations, or commit financial obligations. The only input is a location string, which is safely constrained. Read access to public weather data presents minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Gets the current weather and a short daily forecast' — a read operation with no side effects or data modification capability.
Attacks that exploit this kind of access
The rule that runs get_weather safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_weather, this is the rule to start with:
get_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 Local, apply this rule, and every get_weather call is checked against it from then on.
Questions about get_weather
Gets the current weather and a short daily forecast for a location. Pass a city name ('London', 'San Francisco', 'Tokyo,JP') or 'lat,lon' coordinates. Uses Open-Meteo — no API key required. Location must be provided (there is no device-location access). It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
get_weather accepts 2 parameters: days, location. Required: location. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for get_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 Local. Nothing to install.
get_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 get_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 get_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.
get_weather is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue