get_infrastructure
Nearby infrastructure for a location — substations (count + max voltage_kv within radius), transmission lines (>69 kV path overlay), interstate + lateral gas pipelines, and power plants (operating + planned, by fuel) within configurable radius_km. Returns distance + capacity for each, joined to H...
This record as markdown: /tools/cloud-dchub-mcp-server/get-infrastructure.md
What get_infrastructure does on Mcp Server
AI agents call get_infrastructure 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 | — | Center latitude in decimal degrees (-90 to 90, required), e.g. 33.45 |
lng | number | — | Alias for lon — either name works |
lon | number | — | Center longitude in decimal degrees (-180 to 180, required), e.g. -112.07 |
layer | string | — | Optional single asset layer to return, e.g. substations, transmission, pipelines, power_plants |
limit | integer | — | Max results to return (1-500; default varies by tool) |
latitude | number | — | Alias for lat — either name works |
longitude | number | — | Alias for lon — either name works |
radius_km | number | — | Search radius in kilometers around the point, e.g. 25 |
min_voltage_kv | number | — | Only include transmission/substations at or above this voltage in kV, e.g. 69 |
Parameters from the server's own tool schema.
Why get_infrastructure is rated Low
Tool queries and returns geographic infrastructure data without modifying, executing, or deleting anything.
From the tool's definition retrieves nearby infrastructure data, substations, transmission lines, power plants, capacity information
Attacks that exploit this kind of access
The rule that runs get_infrastructure 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_infrastructure, this is the rule to start with:
get_infrastructure 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_infrastructure call is checked against it from then on.
Questions about get_infrastructure
Nearby infrastructure for a location — substations (count + max voltage_kv within radius), transmission lines (>69 kV path overlay), interstate + lateral gas pipelines, and power plants (operating + planned, by fuel) within configurable radius_km. Returns distance + capacity for each, joined to HIFLD/EIA. Answers "what is near this parcel", "how far is the nearest substation and what voltage is it". Try: get_infrastructure lat=33.45 lon=-112.07 radius_km=25. Returns raw nearby assets; do NOT use for a single scored site-suitability verdict (use analyze_site). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_infrastructure accepts 9 parameters: lat, lng, lon, layer, limit, latitude, longitude, radius_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 get_infrastructure: 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_infrastructure 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_infrastructure 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_infrastructure. 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_infrastructure 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