currentuvindex.weather.uv_index
Get the current UV Index, an hourly forecast for the next ~120 hours, and up to 24 hours of recent history for any latitude/longitude worldwide. Each data point includes a WHO/EPA risk category (Low, Moderate, High, Very High, Extreme). Also returns the peak forecasted UV Index and when it occurs...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/currentuvindex.weather.uv-index.md
What currentuvindex.weather.uv_index does on Apibase
AI agents call currentuvindex.weather.uv_index 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 |
|---|---|---|---|
latitude | number | Yes | Latitude of the location, decimal degrees (-90 to 90). Example: 40.6943. |
longitude | number | Yes | Longitude of the location, decimal degrees (-180 to 180). Example: -73.9249. |
Parameters from the server's own tool schema.
Why currentuvindex.weather.uv_index is rated Low
Retrieves weather data with no side effects or ability to modify state.
From the tool's definition Get current UV Index, hourly forecast, recent history for latitude/longitude worldwide.
Attacks that exploit this kind of access
The rule that runs currentuvindex.weather.uv_index 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 currentuvindex.weather.uv_index, this is the rule to start with:
currentuvindex.weather.uv_index 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 currentuvindex.weather.uv_index call is checked against it from then on.
Questions about currentuvindex.weather.uv_index
Get the current UV Index, an hourly forecast for the next ~120 hours, and up to 24 hours of recent history for any latitude/longitude worldwide. Each data point includes a WHO/EPA risk category (Low, Moderate, High, Very High, Extreme). Also returns the peak forecasted UV Index and when it occurs. Data: currentuvindex.com, CC BY 4.0 license, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
currentuvindex.weather.uv_index accepts 2 parameters: latitude, longitude. Required: latitude, longitude. 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 currentuvindex.weather.uv_index: 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.
currentuvindex.weather.uv_index 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 currentuvindex.weather.uv_index 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 currentuvindex.weather.uv_index. 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.
currentuvindex.weather.uv_index 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