get_water_risk

Use when scoring a US site for cooling-water sustainability — the water-risk factor engineering site-selectors screen before committing to evaporative cooling. Example: "Is this Phoenix parcel water-constrained for a 100MW build?" — get_water_risk lat=33.45 lon=-112.07 (or get_water_risk state=AZ...

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp
Low RISK CLASS
Category Read
Parameters 60 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/get-water-risk.md

What get_water_risk does on Mcp Server

AI agents call get_water_risk 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.

ParameterTypeRequiredDescription
lat number Site latitude in decimal degrees (-90 to 90) for the most precise water-risk read, e.g. 33.45
lng number Alias for lon — either name works
lon number Site longitude in decimal degrees (-180 to 180), e.g. -112.07
state string US state abbreviation as an alternative to lat/lon, e.g. AZ
latitude number Alias for lat — either name works
longitude number Alias for lon — either name works

Parameters from the server's own tool schema.

Why get_water_risk is rated Low

Even though get_water_risk only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about get_water_risk

What does the get_water_risk tool do? +

Use when scoring a US site for cooling-water sustainability — the water-risk factor engineering site-selectors screen before committing to evaporative cooling. Example: "Is this Phoenix parcel water-constrained for a 100MW build?" — get_water_risk lat=33.45 lon=-112.07 (or get_water_risk state=AZ / county=Maricopa). Params: ONE of lat+lon (-90..90 / -180..180), state (2-letter US), or county; lat/lon gives the most precise read. Returns: {water_stress_score (0-100, higher=worse), drought_category (D0-D4), outlook_12mo, cooling_water_assessment, source}. Joined to USGS water-stress + US Drought Monitor. Free tier. Do NOT use for nearby physical infrastructure (use get_infrastructure) or a combined multi-factor site verdict spanning grid+fiber+water+tax+climate (use analyze_site); this covers the WATER factor only. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_water_risk accept? +

get_water_risk accepts 6 parameters: lat, lng, lon, state, latitude, longitude. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_water_risk? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for get_water_risk: 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.

What risk level is get_water_risk? +

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

Can I rate-limit get_water_risk? +

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

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

get_water_risk 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.