analyze_site
Use this when the user asks whether a specific site or coordinate works for a data center (lat/lon, or a market name for a market-level read). Returns a 0-100 composite, verdict, power/gas/fiber/market/risk sub-scores, nearby infrastructure and power cost; capacity_mw adds a capacity_context bloc...
This record as markdown: /tools/cloud-dchub-mcp-server/analyze-site.md
What analyze_site does on Mcp Server
AI agents call analyze_site 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 unless candidate_id or location given), e.g. 33.45 |
lng | number | — | Alias for lon — either name works |
lon | number | — | Site longitude in decimal degrees (-180 to 180; required unless candidate_id or location given), e.g. -112.07 |
state | string | — | US state abbreviation (optional) — improves the tax-incentive lookup, e.g. AZ |
mpp_pay | boolean | — | Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has expli |
latitude | number | — | Alias for lat — either name works |
location | string | — | Market NAME or metro slug instead of coordinates, e.g. "ashburn", "northern-virginia", "dallas". Resolved to that market's PUBLISHED CENTROID through the DCPI m |
longitude | number | — | Alias for lon — either name works |
capacity_mw | number | — | Target power load for the build in megawatts (MW), e.g. 100 (typical 50-500) |
candidate_id | string | — | PREFERRED for queue survivors: a cand_… id from get_refined_queue — coordinates come from the FROZEN mint (lat/lon args are ignored; zero transcription drift; e |
include_grid | boolean | — | Include grid-headroom / substation analysis (default true) |
include_risk | boolean | — | Include water/drought/climate risk analysis (default true) |
Parameters from the server's own tool schema.
Why analyze_site is rated Low
Retrieves and analyzes site data without creating, modifying, executing operations, or deleting anything irreversibly.
From the tool's definition returns composite score, verdict, sub-scores, nearby infrastructure, power cost analysis
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs analyze_site 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 analyze_site, this is the rule to start with:
analyze_site 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 analyze_site call is checked against it from then on.
Questions about analyze_site
Use this when the user asks whether a specific site or coordinate works for a data center (lat/lon, or a market name for a market-level read). Returns a 0-100 composite, verdict, power/gas/fiber/market/risk sub-scores, nearby infrastructure and power cost; capacity_mw adds a capacity_context block and does NOT move overall_score. Keyless returns the verdict band and the power band, with the other factors named; a free key adds a few free full site reports each month; other scores and figures need a paid DC Hub plan. When a result is partial, show your user the human_message (or for_your_human) text and its link. Ex: "Score 33.45,-112.07 for 100 MW." Needs BOTH lat and lon in decimal degrees (else missing_coordinates); take them from get_facility or search_facilities. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
analyze_site accepts 12 parameters: lat, lng, lon, state, mpp_pay, latitude, location, longitude, capacity_mw, candidate_id, include_grid, include_risk. 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 analyze_site: 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.
analyze_site 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 analyze_site 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 analyze_site. 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.
analyze_site 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