get_gas_economics
Behind-the-meter / gas-fired power inputs for a US data-center market: Henry Hub spot, regional basis differential, and the delivered industrial + electric gas tariff ($/MMBtu), each with its own source label. Pass market=<slug> (e.g. "northern-virginia", "dallas", "phoenix"). ★ WITHDRAWN 2026-08...
This record as markdown: /tools/cloud-dchub-mcp-server/get-gas-economics.md
What get_gas_economics does on Mcp Server
AI agents call get_gas_economics 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 |
|---|---|---|---|
market | string | Yes | Market slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank |
heat_rate_btu_per_kwh | number | — | Optional custom generator heat rate in Btu/kWh for the gas-to-grid $/MWh scenario, e.g. 6800 (avg CCGT) |
Parameters from the server's own tool schema.
Why get_gas_economics is rated Low
Tool queries and returns market data without modifying systems or executing operations.
From the tool's definition retrieves gas economics data: Henry Hub spot, basis differential, tariffs
Attacks that exploit this kind of access
The rule that runs get_gas_economics 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_economics, this is the rule to start with:
get_gas_economics 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_economics call is checked against it from then on.
Questions about get_gas_economics
Behind-the-meter / gas-fired power inputs for a US data-center market: Henry Hub spot, regional basis differential, and the delivered industrial + electric gas tariff ($/MMBtu), each with its own source label. Pass market=<slug> (e.g. "northern-virginia", "dallas", "phoenix"). ★ WITHDRAWN 2026-08-08: the gas-to-grid levelized cost ($/MWh across CCGT/peaker heat-rate scenarios) is NO LONGER RETURNED. Five surfaces published a $/MWh for the same market on the same day up to 5.5x apart because each chose the burner-tip price by a different rule, with no sanity gate — this endpoint served a physically impossible $6.73/MWh for Phoenix stamped data_basis: "live". The heat-rate arithmetic was correct; the input price selection was not. The $/MMBtu layers are sourced and still returned; gas_to_grid_status carries the reason. DO NOT quote a cached $/MWh figure, and do not derive one yourself from the $/MMBtu without saying that you did. Do NOT use for the electricity grid fuel mix (use get_grid_data). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_gas_economics accepts 2 parameters: market, heat_rate_btu_per_kwh. Required: market. 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_economics: 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_economics 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_economics 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_economics. 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_economics 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