get_climate_intel
Use this when the user asks about seismic or climate design inputs for a data center site (lat/lon) — the layer that drives data-center structural bracing cost (seismic) and cooling design (cooling degree-days, extreme temps). Grounded STRICTLY in USGS ASCE 7 (seismic) + NOAA climate normals via ...
This record as markdown: /tools/cloud-dchub-mcp-server/get-climate-intel.md
What get_climate_intel does on Mcp Server
AI agents call get_climate_intel to retrieve information from Mcp Server 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 |
|---|---|---|---|
lat | number | — | Site latitude in decimal degrees (-90 to 90, required), e.g. 33.45 |
lng | number | — | Alias for lon — either name works |
lon | number | — | Site longitude in decimal degrees (-180 to 180, required), e.g. -112.07 |
latitude | number | — | Alias for lat — either name works |
longitude | number | — | Alias for lon — either name works |
radius_km | number | — | Max distance (km) to snap to the nearest NOAA station (optional, default 25) |
Parameters from the server's own tool schema.
Why get_climate_intel is rated Low
Tool queries USGS and NOAA data for site analysis with no modifications or external effects.
From the tool's definition retrieves seismic hazard and climate normals data from federal sources; no side effects
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_climate_intel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_climate_intel, this is the rule to start with:
get_climate_intel 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 Mcp Server, apply this rule, and every get_climate_intel call is checked against it from then on.
Questions about get_climate_intel
Use this when the user asks about seismic or climate design inputs for a data center site (lat/lon) — the layer that drives data-center structural bracing cost (seismic) and cooling design (cooling degree-days, extreme temps). Grounded STRICTLY in USGS ASCE 7 (seismic) + NOAA climate normals via ACIS; every value traces to a federal source and missing data is declared unavailable, never estimated. Example: get_climate_intel lat=33.45 lon=-112.07. Returns {seismic_hazard_usgs:{status, peak_ground_acceleration_g, ss, s1, seismic_design_category, hazard_class}, climate_normals_noaa:{status, reference_station:{id,name,distance_km}, cooling_design_metrics:{cooling_degree_days_annual, extreme_max_dry_bulb_f, extreme_max_wet_bulb_f (null if source lacks it), data_vintage}}, overall_climate_summary, data_availability, sources}. radius_km (optional, default 25) snaps to the nearest NOAA station; beyond it climate returns unavailable_exceeds_radius. Seismic is US (ASCE 7); non-US → seismic unavailable. For natural-hazard ratings use get_disaster_risk; for one blended verdict use get_composite_site_score. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_climate_intel accepts 6 parameters: lat, lng, lon, latitude, longitude, radius_km. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for get_climate_intel: 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 Mcp Server. Nothing to install.
get_climate_intel 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 get_climate_intel 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 get_climate_intel. 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.
get_climate_intel is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue