Get current weather for the default location
AI agents call get_local_weather to retrieve information from Weather MCP Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current weather information for a predefined location without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, making it the lowest risk category. Low severity is appropriate as misuse would only expose publicly available weather data.
From the tool's definition Tool name 'get_local_weather' and description 'Get current weather for the default location' indicate data retrieval with no modification or execution of external operations. The server description confirms it 'Provides live weather data' as a read operation.
Attacks that exploit this kind of access
Get current weather for the default location. It is categorised as a Read tool in the Weather MCP Service MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP Service MCP server in PolicyLayer and add a rule for get_local_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 Weather MCP Service. Nothing to install.
get_local_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_local_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_local_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_local_weather is provided by the Weather MCP Service MCP server (philip-walsh/weathernode). 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 →