weather.weatherapi.current
Get current weather conditions for any location worldwide — temperature, wind, humidity, pressure, UV index, cloud cover, feels-like temp. Accepts city name, coordinates, zip code, or airport code. 100K+ stations globally (WeatherAPI.com)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/weather.weatherapi.current.md
What weather.weatherapi.current does on Apibase
AI agents call weather.weatherapi.current to retrieve information from Apibase 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 |
|---|---|---|---|
q | string | Yes | Location query — city name (e.g. "London"), coordinates ("48.8,2.35"), US zip ("10001"), UK postcode ("SW1"), IP address, or IATA airport code ("JFK") |
Parameters from the server's own tool schema.
Why weather.weatherapi.current is rated Low
Tool retrieves real-time weather data without modifying any state or resources.
From the tool's definition Get current weather conditions for any location worldwide — temperature, wind, humidity, pressure, UV index, cloud cover, feels-like temp.
Attacks that exploit this kind of access
The rule that runs weather.weatherapi.current safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For weather.weatherapi.current, this is the rule to start with:
weather.weatherapi.current 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 Apibase, apply this rule, and every weather.weatherapi.current call is checked against it from then on.
Questions about weather.weatherapi.current
Get current weather conditions for any location worldwide — temperature, wind, humidity, pressure, UV index, cloud cover, feels-like temp. Accepts city name, coordinates, zip code, or airport code. 100K+ stations globally (WeatherAPI.com). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
weather.weatherapi.current accepts 1 parameter: q. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for weather.weatherapi.current: 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 Apibase. Nothing to install.
weather.weatherapi.current 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 weather.weatherapi.current 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 weather.weatherapi.current. 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.
weather.weatherapi.current is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue