get_weather
Get current weather conditions for any city. Uses Open-Meteo (free, no key) after geocoding the city via Nominatim. Returns temperature, wind speed, weather code, and conditions. Parameters: city — City name to get weather for (required), e.g. "London".
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/get-weather.md
What get_weather does on X402 Middleware
AI agents call get_weather 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_weather is rated Low
This tool queries a public weather API (Open-Meteo) and returns weather data. It performs a simple lookup operation without side effects, state changes, or irreversible actions. The lack of financial impact, code execution, or data modification clearly places it in the Read category with low severity.
From the tool's definition Tool description states 'Get current weather conditions for any city' and 'Returns temperature, wind speed, weather code, and conditions.' These are read-only retrieval operations with no data modification, deletion, or external effects.
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 X402 Middleware, 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 X402 Middleware, apply this rule, and every get_weather call is checked against it from then on.
Questions about get_weather
Get current weather conditions for any city. Uses Open-Meteo (free, no key) after geocoding the city via Nominatim. Returns temperature, wind speed, weather code, and conditions. Parameters: city — City name to get weather 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_weather 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_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 X402 Middleware. 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 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