get_infrastructure

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 90 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-infrastructure.md

WHAT IT DOES

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.

RISK

Why get_infrastructure is rated Low

Even though get_infrastructure 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

get_infrastructure is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_infrastructure": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about get_infrastructure

What does the get_infrastructure tool do? +

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

What parameters does get_infrastructure accept? +

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.

How do I enforce a policy on get_infrastructure? +

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.

What risk level is get_infrastructure? +

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

Can I rate-limit get_infrastructure? +

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.

How do I block get_infrastructure completely? +

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.

What MCP server provides get_infrastructure? +

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.

KEEP EXPLORING

More on Mcp Server, and thousands of servers like it.

This server

All 79 Mcp Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →