get_forecast
Get a 7-day weather forecast for any city. Uses Open-Meteo (free, no key) after geocoding the city via Nominatim. Returns daily high/low temps, precipitation, and weather codes. Parameters: city — City name to get forecast for (required), e.g. "London".
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/get-forecast.md
What get_forecast does on X402 Middleware
AI agents call get_forecast to retrieve information from X402 Middleware 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 |
|---|---|---|---|
city | string | Yes |
Parameters from the server's own tool schema.
Why get_forecast is rated Low
This tool queries weather data from Open-Meteo and Nominatim APIs based on a city parameter. It retrieves and returns structured weather information without any side effects, state changes, or ability to modify data.
From the tool's definition Tool description states it 'Get[s] a 7-day weather forecast' and 'Returns daily high/low temps, precipitation, and weather codes.' The verb 'Get' and 'Returns' indicate data retrieval with no modification, creation, deletion, or execution of external…
Attacks that exploit this kind of access
The rule that runs get_forecast safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_forecast, this is the rule to start with:
get_forecast 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 X402 Middleware, apply this rule, and every get_forecast call is checked against it from then on.
Questions about get_forecast
Get a 7-day weather forecast for any city. Uses Open-Meteo (free, no key) after geocoding the city via Nominatim. Returns daily high/low temps, precipitation, and weather codes. Parameters: city — City name to get forecast for (required), e.g. "London". It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
get_forecast accepts 1 parameter: city. Required: city. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for get_forecast: 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 X402 Middleware. Nothing to install.
get_forecast 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_forecast 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_forecast. 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_forecast is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue