get_power_pipeline
Use this when the user asks where new power generation is coming online (the forward supply pipeline) — e.g. "how much new generation is planned in Virginia / the Southeast / ERCOT, and when?". Planned, permitting, and under-construction generators NATIONWIDE from EIA-860M, INCLUDING non-ISO regi...
This record as markdown: /tools/cloud-dchub-mcp-server/get-power-pipeline.md
What get_power_pipeline does on Mcp Server
AI agents call get_power_pipeline 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 |
|---|---|---|---|
ba | string | — | Balancing-authority / ISO code, e.g. PJM, ERCO, SOCO, TVA, AZPS |
limit | integer | — | Max results to return (1-500; default varies by tool) |
state | string | — | US state abbreviation to filter generators, e.g. VA, TX |
min_mw | number | — | Minimum nameplate capacity filter in megawatts (MW) |
status | string | — | Generator status code: P/L/T (planned), U/V (under construction), TS (testing) |
Parameters from the server's own tool schema.
Why get_power_pipeline is rated Low
Tool queries and retrieves publicly available energy infrastructure data without modification or execution.
From the tool's definition retrieves planned power generation pipeline data, forward supply forecasts nationwide.
Attacks that exploit this kind of access
The rule that runs get_power_pipeline 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_power_pipeline, this is the rule to start with:
get_power_pipeline 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_power_pipeline call is checked against it from then on.
Questions about get_power_pipeline
Use this when the user asks where new power generation is coming online (the forward supply pipeline) — e.g. "how much new generation is planned in Virginia / the Southeast / ERCOT, and when?". Planned, permitting, and under-construction generators NATIONWIDE from EIA-860M, INCLUDING non-ISO regions (TVA, Southern Co, Arizona PS, PacifiCorp, LADWP) that interconnection-queue feeds miss. Each generator has location (lat/lng), state, county, balancing authority, technology/fuel (solar photovoltaic, onshore wind, natural-gas combined cycle, batteries, nuclear), nameplate megawatts (MW), status (planned → under construction), and planned online month/year. Filter by state (2-letter, e.g. VA), ba (balancing-authority/ISO code, e.g. PJM, ERCO, SOCO, TVA), status (P/L/T=planned, U/V=under construction, TS=testing), or min_mw. Returns a summary (total planned MW, mix by technology + status) plus the largest projects. Answers "how much new generation is planned in Virginia and when does it land". Try: get_power_pipeline state=VA. Do NOT use for ALREADY-OPERATING capacity or grid headroom (use get_grid_intelligence / get_grid_data) or for data-center construction projects (use get_pipeline). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_power_pipeline accepts 5 parameters: ba, limit, state, min_mw, status. 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_power_pipeline: 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_power_pipeline 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_power_pipeline 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_power_pipeline. 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_power_pipeline 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