Low Risk

get_climate_data

World Bank CCKP climate data for any country: historical observations and CMIP6 climate-model projections. Returns mean temperature, max/min temperature, or precipitation, by emissions scenario. Pass the components as separate args — this tool assembles the brittle composite "indicator code" for ...

Part of the Worldbank Climate server.

get_climate_data is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE WORLDBANK CLIMATE →

Free to start. No card required.

AI agents call get_climate_data to retrieve information from Worldbank Climate without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_climate_data only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_climate_data": {}
  }
}

See the full Worldbank Climate policy for all 22 tools.

Get this rule live on your own Worldbank Climate server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WORLDBANK CLIMATE →

View all 22 tools →

These attack patterns abuse exactly the kind of access get_climate_data gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_climate_data only ever does what you allow.

SECURE WORLDBANK CLIMATE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_climate_data tool do? +

World Bank CCKP climate data for any country: historical observations and CMIP6 climate-model projections. Returns mean temperature, max/min temperature, or precipitation, by emissions scenario. Pass the components as separate args — this tool assembles the brittle composite "indicator code" for you. Values are returned keyed by ISO3 country code; the inner key is "<startYear>-07" (annual/period) or per-season months. WORKED EXAMPLES (all verified live): 1. Historical annual mean temperature for the USA (defaults): {"geography":"USA"} => tas climatology over 1995-2014, ~10.2°C. 2. Projected warming (anomaly) for the USA mid-century under a high scenario: {"geography":"USA","scenario":"ssp585","period":"2040-2059","product":"anomaly"} => ~2.4°C above baseline. 3. Historical annual precipitation for all countries: {"geography":"all_countries","variable":"pr","product":"climatology","period":"1995-2014","scenario":"historical"} => mm/year per country. If assembly ever fails for an exotic combination, pass the full composite string via indicator_code instead.. It is categorised as a Read tool in the Worldbank Climate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_climate_data? +

Register the Worldbank Climate MCP server in PolicyLayer and add a rule for get_climate_data: 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 Worldbank Climate. Nothing to install.

What risk level is get_climate_data? +

get_climate_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_climate_data? +

Yes. Add a rate_limit block to the get_climate_data 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.

How do I block get_climate_data completely? +

Set action: deny in the PolicyLayer policy for get_climate_data. 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.

What MCP server provides get_climate_data? +

get_climate_data is provided by the Worldbank Climate MCP server (https://gateway.pipeworx.io/worldbank-climate/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Worldbank Climate tool call.

Deterministic rules across all 22 Worldbank Climate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.