climate.indicators.arctic_ice
Arctic sea ice extent from NSIDC — monthly measurements in million km² since 1979. Tracks long-term decline in Arctic ice coverage. Returns last 10 years by default. Source: National Snow and Ice Data Center.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/climate.indicators.arctic-ice.md
What climate.indicators.arctic_ice does on Apibase
AI agents call climate.indicators.arctic_ice 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 |
|---|---|---|---|
years | integer | — | Number of years of data to return (1-50, default 10). Data is monthly. |
Parameters from the server's own tool schema.
Why climate.indicators.arctic_ice is rated Low
Tool queries and returns Arctic ice measurements; no side effects, data creation, or resource impact.
From the tool's definition monthly measurements, tracks, returns — retrieves historical climate data
Attacks that exploit this kind of access
The rule that runs climate.indicators.arctic_ice 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 climate.indicators.arctic_ice, this is the rule to start with:
climate.indicators.arctic_ice 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 climate.indicators.arctic_ice call is checked against it from then on.
Questions about climate.indicators.arctic_ice
Arctic sea ice extent from NSIDC — monthly measurements in million km² since 1979. Tracks long-term decline in Arctic ice coverage. Returns last 10 years by default. Source: National Snow and Ice Data Center. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
climate.indicators.arctic_ice accepts 1 parameter: years. 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 climate.indicators.arctic_ice: 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.
climate.indicators.arctic_ice 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 climate.indicators.arctic_ice 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 climate.indicators.arctic_ice. 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.
climate.indicators.arctic_ice 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