get_infra_projects
Use this when the user asks what gas pipeline or transmission line projects are planned, proposed, approved or under construction — the forward build-out, not the existing network. e.g. "which interstate gas pipelines are under construction into Louisiana?", "what 345 kV transmission projects are...
This record as markdown: /tools/cloud-dchub-mcp-server/get-infra-projects.md
What get_infra_projects does on Mcp Server
AI agents call get_infra_projects 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 |
|---|---|---|---|
type | string | — | Which project list: gas_pipeline (EIA, US-wide), transmission (ERCOT TPIT, Texas only) or all (default) |
limit | integer | — | Max results to return (1-500; default varies by tool) |
state | string | — | US state abbreviation, e.g. TX or LA. Gas projects match any state they cross; transmission projects are all TX |
min_kv | number | — | Transmission only: minimum voltage in kilovolts (kV), e.g. 345. With type=all it narrows to transmission projects |
status | string | — | Status, case-insensitive; comma list allowed. Gas: Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed. Transmission: Planned, Conceptua |
new_since | string | — | Only projects DC Hub first saw on or after this date (YYYY-MM-DD). The initial backfill is never counted as new |
min_capacity | number | — | Gas only: minimum pipeline capacity in million cubic feet per day (MMcf/d), e.g. 1000. With type=all it narrows to gas projects |
in_service_after | string | — | Only projects entering service on or after this date (YYYY-MM-DD or YYYY). Gas compares the in-service year; transmission the actual, else projected, in-service |
include_delisted | boolean | — | Also return projects the latest source release no longer lists (completed, withdrawn or dropped). Default false |
in_service_before | string | — | Only projects entering service on or before this date (YYYY-MM-DD or YYYY) |
Parameters from the server's own tool schema.
Why get_infra_projects is rated Low
Tool retrieves and queries forward-looking infrastructure project data without side effects or data modification.
From the tool's definition queries planned infrastructure projects; retrieves public EIA data; no modifications
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs get_infra_projects 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_infra_projects, this is the rule to start with:
get_infra_projects 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_infra_projects call is checked against it from then on.
Questions about get_infra_projects
Use this when the user asks what gas pipeline or transmission line projects are planned, proposed, approved or under construction — the forward build-out, not the existing network. e.g. "which interstate gas pipelines are under construction into Louisiana?", "what 345 kV transmission projects are planned in PJM by 2030?", "what new projects appeared since last month?". COVERS: (1) natural gas pipeline projects US-wide from the EIA natural gas pipeline projects list (public domain) — operator, status (Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed), states crossed, capacity in MMcf/d, miles, cost in $M, diameter, FERC/state docket, in-service year; (2) transmission projects from five ISOs' own project lists — ERCOT (TPIT), PJM (RTEP), MISO (MTEP Appendix A), SPP (STEP) and ISO-NE (RSP list); NOT CAISO or NYISO, and not utilities outside those ISOs. Each ISO publishes a different grain (an upgrade or facility, not a whole project), so a row count is a count of upgrades. Answers "what gas pipelines are being built into Louisiana, how much capacity do they add, and when do they enter service". Try: get_infra_projects type=gas_pipeline state=LA status=Construction. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_infra_projects accepts 10 parameters: type, limit, state, min_kv, status, new_since, min_capacity, in_service_after, include_delisted, in_service_before. 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_infra_projects: 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_infra_projects 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_infra_projects 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_infra_projects. 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_infra_projects 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