find_sites
Use this when the user has no data center site yet and wants candidate search areas (site selection by substation voltage, gas and fiber distance); execute_plan covers a multi-part siting question. THE INVERSE QUERY: every other DC Hub siting tool needs a coordinate you already have — analyze_sit...
This record as markdown: /tools/cloud-dchub-mcp-server/find-sites.md
What find_sites does on Mcp Server
AI agents call find_sites 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 | — | Latitude of a search centre, e.g. 39.04 — use with lon (+ radius_km) instead of state |
lng | number | — | Alias for lon — either name works |
lon | number | — | Longitude of a search centre, e.g. -77.48 |
limit | integer | — | Max results to return (1-500; default varies by tool) |
state | string | — | 2-letter US state to search, e.g. OH — required unless you pass lat + lon |
latitude | number | — | Alias for lat — either name works |
longitude | number | — | Alias for lon — either name works |
radius_km | number | — | Search radius in km around lat/lon (default 80, clamped 5-400); ignored in state mode |
cluster_km | number | — | Collapse anchors within this many km into one candidate area (default 8, max 100). Raise it for broader coverage, lower it for denser results |
max_gas_km | number | — | Drop candidates farther than this from the nearest gas pipeline. Applied ONLY if the gas layer answers — check constraint_coverage |
max_fiber_km | number | — | Drop candidates farther than this from the nearest fiber route (CHORD approximation — see fiber_distance_basis). Applied ONLY if the fiber layer answers |
min_voltage_kv | number | — | Only anchor on substations at or above this voltage in kV (default 115). 230+ for hyperscale, 500 for the largest campuses |
Parameters from the server's own tool schema.
Why find_sites is rated Low
Retrieves and searches data center site candidates; returns information without modifying or deleting data.
From the tool's definition candidate search areas, returns, query, no side effects, informational
Risk signalsHigh parameter count (13 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs find_sites 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 find_sites, this is the rule to start with:
find_sites 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 find_sites call is checked against it from then on.
Questions about find_sites
Use this when the user has no data center site yet and wants candidate search areas (site selection by substation voltage, gas and fiber distance); execute_plan covers a multi-part siting question. THE INVERSE QUERY: every other DC Hub siting tool needs a coordinate you already have — analyze_site scores one, get_composite_site_score grades one, rank_sites orders candidates YOU already enriched, find_alternatives needs a seed facility. This one answers "where should I even be looking?". Returns candidate SEARCH AREAS anchored on real HIFLD substations at or above min_voltage_kv, spatially de-duplicated by cluster_km so a dense metro yields distinct areas instead of 40 near-identical rows, each carrying measured distance to the nearest gas pipeline and fiber route plus state-grain moratorium context, and a next_calls handoff. Answers "where should I even be looking for 200 MW in Ohio" and "which areas near Dallas sit on 230kV with gas within 5 miles". Try: find_sites state=OH min_voltage_kv=230 max_gas_km=8 — or find_sites lat=39.04 lon=-77.48 radius_km=60 min_voltage_kv=500. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
find_sites accepts 12 parameters: lat, lng, lon, limit, state, latitude, longitude, radius_km, cluster_km, max_gas_km, max_fiber_km, min_voltage_kv. 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 find_sites: 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.
find_sites 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 find_sites 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 find_sites. 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.
find_sites 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