weather.conditions.forecast
Get weather forecast for a location
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/weather.conditions.forecast.md
What weather.conditions.forecast does on Apibase
AI agents call weather.conditions.forecast 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 |
|---|---|---|---|
type | string | — | Forecast granularity: hourly, daily, or both |
units | string | — | Temperature units system |
location | string | Yes | City name, coordinates (lat,lon), or zip code |
Parameters from the server's own tool schema.
Why weather.conditions.forecast is rated Low
Forecasts are data retrieval only, with no reversible or irreversible side effects.
From the tool's definition Get weather forecast for a location; retrieves data, no side effects.
Attacks that exploit this kind of access
The rule that runs weather.conditions.forecast 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.conditions.forecast, this is the rule to start with:
weather.conditions.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 Apibase, apply this rule, and every weather.conditions.forecast call is checked against it from then on.
Questions about weather.conditions.forecast
Get weather forecast for a location. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
weather.conditions.forecast accepts 3 parameters: type, units, location. Required: location. 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.conditions.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 Apibase. Nothing to install.
weather.conditions.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 weather.conditions.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 weather.conditions.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.
weather.conditions.forecast 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