get_gas_intelligence
Use when a human asks about gas-fired or behind-the-meter power economics for a data center in a US state — "is gas power cheaper than the grid in Texas?", "what is the gas access + pipeline situation in Virginia?". The GAS analogue of get_grid_intelligence: fuses the DC Hub Gas Index (DCGI), liv...
This record as markdown: /tools/cloud-dchub-mcp-server/get-gas-intelligence.md
What get_gas_intelligence does on Mcp Server
AI agents call get_gas_intelligence 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 |
|---|---|---|---|
state | string | — | Alias for region — the US state code or name |
region | string | — | US state code or name (required), e.g. "TX", "Texas", "Virginia" |
Parameters from the server's own tool schema.
Why get_gas_intelligence is rated Low
Tool queries and aggregates existing energy market data without side effects or state changes.
From the tool's definition retrieves gas intelligence, pipeline data, pricing analytics — no modifications
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_gas_intelligence 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_gas_intelligence, this is the rule to start with:
get_gas_intelligence 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_gas_intelligence call is checked against it from then on.
Questions about get_gas_intelligence
Use when a human asks about gas-fired or behind-the-meter power economics for a data center in a US state — "is gas power cheaper than the grid in Texas?", "what is the gas access + pipeline situation in Virginia?". The GAS analogue of get_grid_intelligence: fuses the DC Hub Gas Index (DCGI), live Henry Hub, gas-to-grid $/MWh across heat-rate scenarios, pipeline-operator presence, and the live grid gas share into one per-STATE brief. Params: region (US state code or name, e.g. "TX" | "Texas" | "Virginia"). Returns: {region, region_name, gas_access (pipeline counts + operators — PRESENCE not firm capacity), henry_hub_usd_mmbtu (live), basis_usd_mmbtu (synthetic-labeled), delivered_price_usd_mmbtu (null where the tariff table is sparse — surfaced honestly, never fabricated), live_grid_gas_share_pct, pipeline_presence (operators + parent midstreams), data_basis (per-field provenance/confidence), omitted_no_fabrication, dcgi_status, gas_to_grid_status}. ★ ★ TWO DIFFERENT STATES, do not merge them. dcgi_score and dcgi_verdict were withdrawn 2026-08-08 and RESTORED 2026-08-30 once all three defective terms were repaired — they are returned again, but a figure published before 2026-08-08 is from a different index and must not be compared with one published now (/api/v1/dcgi/methodology corrections). gas_to_grid_usd_per_mwh and the behind-the-meter-vs-grid delta remain WITHDRAWN and are still NOT returned: five surfaces disagreed by up to 5.5x on the same market's $/MWh with no sanity gate, and that defect is not fixed. dcgi_status and gas_to_grid_status carry the current state of each — read them rather than assuming both moved together. DO NOT quote a cached DCGI score or $/MWh. Everything else in this brief — live Henry Hub, live ISO gas share, pipeline and parent-midstream presence — is unaffected and is what this tool is now for. Every field carries a data_basis label; gas storage / LNG / firm pipeline capacity are deliberately OMITTED (no feed). Do NOT use for electricity grid headroom (use get_grid_intelligence) or the DCGI score alone (use get_gas_index). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_gas_intelligence accepts 2 parameters: state, region. 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_gas_intelligence: 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_gas_intelligence 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_gas_intelligence 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_gas_intelligence. 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_gas_intelligence 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