get_hosting_capacity
Use this when the user asks how many MW a distribution feeder can take: utility-published hosting capacity — the MW a NAMED distribution feeder can actually take, straight from the utility's own hosting-capacity GIS. Published records from many utilities (e.g. Con Edison, National Grid NY/MA, NYS...
This record as markdown: /tools/cloud-dchub-mcp-server/get-hosting-capacity.md
What get_hosting_capacity does on Mcp Server
AI agents call get_hosting_capacity 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 the point to search around, decimal degrees. Must be paired with lon. |
lng | number | — | Alias for lon — either name works |
lon | number | — | Longitude of the point to search around, decimal degrees. Must be paired with lat. |
limit | integer | — | Max results to return (1-500; default varies by tool) |
market | string | — | Alias for utility — either name works (e.g. "Northern Virginia · Richmond", "New York City · Westchester"). |
min_mw | number | — | Only return feeders whose published capacity is at or above this many MW. |
utility | string | — | Utility or market name, case-insensitive substring — e.g. "Ameren Illinois", "Con Edison", "Providence". Searches that utility's whole published territory inste |
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 25, max 150). Ignored when utility/market is passed — that mode covers the utility's entire published extent. |
capacity_type | string | — | Restrict to one published type: "load" (what a new data-center load can DRAW — the type that answers siting), "gen" (DER/generation EXPORT headroom — NOT availa |
Parameters from the server's own tool schema.
Why get_hosting_capacity is rated Low
Tool queries and retrieves immutable public utility data without modification or execution.
From the tool's definition retrieves utility-published hosting capacity records from GIS; no side effects.
Risk signalsHigh parameter count (11 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_hosting_capacity 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_hosting_capacity, this is the rule to start with:
get_hosting_capacity 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_hosting_capacity call is checked against it from then on.
Questions about get_hosting_capacity
Use this when the user asks how many MW a distribution feeder can take: utility-published hosting capacity — the MW a NAMED distribution feeder can actually take, straight from the utility's own hosting-capacity GIS. Published records from many utilities (e.g. Con Edison, National Grid NY/MA, NYSEG/RG&E, Rhode Island Energy, Orange & Rockland, Central Hudson, Eversource CT, BGE, Pepco/Delmarva/ACE, Dominion VA, Ameren Illinois, AEP Ohio & I&M, Xcel MN/CO, DTE, Avista; the no-args call lists current coverage). This is filed distribution-level truth, not a proximity proxy. Three ways to call it: lat+lon (+radius_km, default 25) for a point; utility or market for a whole published territory; NO ARGS for the coverage list of every market that has data. Answers "can this feeder actually take 20 MW", "where can I plug in without waiting on a substation upgrade". Try: get_hosting_capacity utility="Ameren Illinois" capacity_type=load min_mw=5. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_hosting_capacity accepts 11 parameters: lat, lng, lon, limit, market, min_mw, utility, latitude, longitude, radius_km, capacity_type. 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_hosting_capacity: 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_hosting_capacity 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_hosting_capacity 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_hosting_capacity. 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_hosting_capacity 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