Real-time weather data and 3-day forecast for any location worldwide. Accepts city name or lat/lon coordinates. Returns temperature, humidity, wind, precipitation, and conditions. Powered by Open-Meteo. (Paid via x402: $0.001 USDC per call on Base, settled automatically.)
AI agents call navi_weather to retrieve information from Navi X402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | string | — | Latitude (e.g. 1.3521). Use with lon. |
lon | string | — | Longitude (e.g. 103.8198). Use with lat. |
location | string | — | City or place name (e.g. Singapore, Paris, New York). Alternative to lat/lon. |
Parameters from the server's own tool schema.
This tool queries weather information and returns data without side effects. It is a straightforward read operation. The payment mechanism is automatic and not controlled by the tool itself—it is infrastructure-level billing that does not constitute a financial action by the agent. The only risk is information disclosure, which is minimal for publicly available weather data.
From the tool's definition Tool retrieves weather data: 'Real-time weather data and 3-day forecast for any location worldwide... Returns temperature, humidity, wind, precipitation, and conditions.' No modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
Real-time weather data and 3-day forecast for any location worldwide. Accepts city name or lat/lon coordinates. Returns temperature, humidity, wind, precipitation, and conditions. Powered by Open-Meteo. (Paid via x402: $0.001 USDC per call on Base, settled automatically.). It is categorised as a Read tool in the Navi X402 MCP Server, which means it retrieves data without modifying state.
navi_weather accepts 3 parameters: lat, lon, location. The full parameter table on this page comes from the server's own tool schema.
Register the Navi X402 MCP server in PolicyLayer and add a rule for navi_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 Navi X402. Nothing to install.
navi_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 navi_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 navi_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.
navi_weather is provided by the Navi X402 MCP server (navi-x402-mcp). 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 →