climate_scenario_rcp

SERVERGapup Mcp SOURCEhttps://mcp.gapup.io/mcp

Low RISK CLASS

Category Read

Parameters 63 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-gapup-mcp/climate-scenario-rcp.md

WHAT IT DOES

What climate_scenario_rcp does on Gapup Mcp

AI agents call climate_scenario_rcp to retrieve information from Gapup Mcp 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
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`metrics`	array	—	Métriques à inclure. Défaut : toutes.
`location`	object	Yes	Localisation : {city, country?} ou {lat, lon}
`scenario`	string	Yes	Scénario IPCC. 'all' génère une comparaison multi-scénarios.
`horizon_year`	number	Yes	Année horizon de la projection (2030–2100)
`compare_baseline`	boolean	—	Comparer vs baseline 1990-2010 (défaut true)

Parameters from the server's own tool schema.

RISK

Why climate_scenario_rcp is rated Low

This tool retrieves and projects climate data based on IPCC scenarios for any location. It is purely a read/query operation — fetching long-term climate projections, metrics, and business impact signals. There are no write, execute, destructive, or financial side effects described.

From the tool's definition Projections climatiques long terme... Sorties : comparaison multi-scénarios, probabilité IPCC, signaux d'impact business par secteur. Sources : Open

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs climate_scenario_rcp safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For climate_scenario_rcp, this is the rule to start with:

climate_scenario_rcp Allowed

climate_scenario_rcp is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "climate_scenario_rcp": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every climate_scenario_rcp call is checked against it from then on.

FAQ

Questions about climate_scenario_rcp

What does the climate_scenario_rcp tool do? +

Projections climatiques long terme par scénario IPCC (RCP AR5 + SSP AR6) pour toute localisation. Scénarios : RCP_4_5, RCP_8_5 (AR5), SSP1_2_6, SSP2_4_5, SSP3_7_0, SSP5_8_5 (AR6), ou 'all' (compare tous). Horizons : 2030–2100. Métriques : température (delta vs baseline 1990-2010, jours >35°C, nuits chaudes), précipitations (delta%, événements extrêmes, sécheresses), hausse du niveau de la mer (cm vs 2000), événements extrêmes (ouragans, inondations P100, sécheresses), indice incendie. Sorties : comparaison multi-scénarios, probabilité IPCC, signaux d'impact business par secteur. Sources : Open-Meteo CMIP6 (keyless), IPCC AR6 Atlas lookup, NOAA SLR projections. Usages : TCFD/CSRD physical risk, due diligence actifs long terme, assurance catastrophe, planification infrastructure. Cache 7j. SLA ≤20s. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does climate_scenario_rcp accept? +

climate_scenario_rcp accepts 6 parameters: async, metrics, location, scenario, horizon_year, compare_baseline. Required: location, scenario, horizon_year. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on climate_scenario_rcp? +

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

What risk level is climate_scenario_rcp? +

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

Can I rate-limit climate_scenario_rcp? +

Yes. Add a rate_limit block to the climate_scenario_rcp 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 climate_scenario_rcp completely? +

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

climate_scenario_rcp is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gapup, and thousands of servers like it.

This server

All 271 Gapup tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →