Stream weather updates for a location with periodic updates
AI agents call stream_weather to retrieve information from MCP Weather Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool falls under the Read category as it queries and streams weather data from the Open-Meteo API. The severity is low because weather data retrieval has no side effects, cannot harm systems, and poses no security risk even if called repeatedly or with arbitrary locations. Confidence is high because the name and description clearly indicate a passive data retrieval operation.
From the tool's definition Tool 'stream_weather' retrieves and streams real-time weather data for a location. The description and server context indicate it performs data retrieval operations without modifying, deleting, or executing arbitrary code.
Documented attack patterns abuse exactly the kind of access stream_weather gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Weather Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stream_weather:
{
"version": "1",
"default": "deny",
"tools": {
"stream_weather": {}
}
}stream_weather is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Stream weather updates for a location with periodic updates. It is categorised as a Read tool in the MCP Weather Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Weather Server MCP server in PolicyLayer and add a rule for stream_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 Weather Server. Nothing to install.
stream_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 stream_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 stream_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.
stream_weather is provided by the MCP Weather Server MCP server (tjarriault/mcp-weather-sample). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Weather Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Weather Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.