Compare climate projections across multiple scenarios side by side. Fetches data for each scenario in parallel and displays a comparison table at key time horizons. Args: country_iso: ISO 3166-1 alpha-3 country code. See climate://countries resource for all valid codes. ...
Part of the Climate Impacts MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call compare_scenarios to retrieve information from Climate Impacts 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 compare_scenarios 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.
tools:
compare_scenarios:
rules:
- action: allowSee the full Climate Impacts policy for all 8 tools.
Agents calling read-class tools like compare_scenarios have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Compare climate projections across multiple scenarios side by side. Fetches data for each scenario in parallel and displays a comparison table at key time horizons. Args: country_iso: ISO 3166-1 alpha-3 country code. See climate://countries resource for all valid codes. variable: Climate variable ID (e.g. 'tasAdjust', 'prAdjust'). See climate://variables resource for all valid IDs — do NOT guess. scenarios: List of scenario IDs to compare (e.g. ['o_1p5c', 'h_cpol', 'h_ndc']). See climate://scenarios resource for all valid IDs. season: Season — one of 'annual', 'MAM', 'JJA', 'SON', 'DJF'. Default: 'annual'. spatial_weighting: Spatial aggregation method. Default: 'area'. time_horizons: Years to show in comparison. Default: [2030, 2050, 2100]. . It is categorised as a Read tool in the Climate Impacts MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for compare_scenarios. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Climate Impacts MCP server.
compare_scenarios 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 compare_scenarios rule in your Intercept 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 Intercept policy for compare_scenarios. 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.
compare_scenarios is provided by the Climate Impacts MCP server (valentinlemaire/climate-impacts). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept