getCurrentWeather
Get current weather, wind speed and direction, humidity, and temperature data by city, ZIP code, or geolocation coordinates (latitude/longitude). One of the following parameter combinations must be provided: lat and lon; or city, state (optional), and country (optional).
This record as markdown: /tools/com-api-ninjas-mcp/getcurrentweather.md
What getCurrentWeather does on API Ninjas
AI agents call getCurrentWeather to retrieve information from API Ninjas 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 |
|---|---|---|---|
lat | string | — | Latitude of desired location. |
lon | string | — | Longitude of desired location. |
zip | string | — | 5 digit Zip code (United States only). Premium subscribers only. |
city | string | — | City name. Premium subscribers only. |
state | string | — | US state (for United States cities only). Premium subscribers only. |
country | string | — | Country name. Premium subscribers only. |
Parameters from the server's own tool schema.
Why getCurrentWeather is rated Low
Even though getCurrentWeather only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs getCurrentWeather safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getCurrentWeather, this is the rule to start with:
getCurrentWeather 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 API Ninjas, apply this rule, and every getCurrentWeather call is checked against it from then on.
Questions about getCurrentWeather
Get current weather, wind speed and direction, humidity, and temperature data by city, ZIP code, or geolocation coordinates (latitude/longitude). One of the following parameter combinations must be provided: lat and lon; or city, state (optional), and country (optional). It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getCurrentWeather accepts 6 parameters: lat, lon, zip, city, state, country. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getCurrentWeather: 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 API Ninjas. Nothing to install.
getCurrentWeather 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 getCurrentWeather 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 getCurrentWeather. 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.
getCurrentWeather is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue