eia_natural_gas
US natural gas data from EIA. Series options: 'spot' (Henry Hub daily), 'futures' (NYMEX front-month daily), 'residential' (monthly retail to households), 'storage' (weekly working gas in storage). Default 'spot'.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/eia-natural-gas.md
What eia_natural_gas does on Livedatalink
AI agents call eia_natural_gas to retrieve information from Livedatalink 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 |
|---|---|---|---|
end | string | — | Inclusive upper-bound period (ISO date or YYYY-MM). |
limit | number | — | Maximum rows to return (default 50, max 5000). |
start | string | — | Inclusive lower-bound period (ISO date or YYYY-MM depending on series cadence). |
series | string | — | Subset to query: 'spot', 'futures', 'residential', 'storage'. Default 'spot'. |
Parameters from the server's own tool schema.
Why eia_natural_gas is rated Low
This tool queries publicly available energy market data from the U.S. Energy Information Administration. It has no side effects, cannot modify or delete data, and presents no financial risk (reading market prices is not executing trades). The blast radius of misuse is minimal—worst case, an agent retrieves inaccurate or stale gas prices for informational purposes.
From the tool's definition The tool retrieves 'US natural gas data from EIA' with options to query different data series ('spot', 'futures', 'residential', 'storage').
Attacks that exploit this kind of access
The rule that runs eia_natural_gas safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eia_natural_gas, this is the rule to start with:
eia_natural_gas 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 Livedatalink, apply this rule, and every eia_natural_gas call is checked against it from then on.
Questions about eia_natural_gas
US natural gas data from EIA. Series options: 'spot' (Henry Hub daily), 'futures' (NYMEX front-month daily), 'residential' (monthly retail to households), 'storage' (weekly working gas in storage). Default 'spot'. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
eia_natural_gas accepts 4 parameters: end, limit, start, series. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for eia_natural_gas: 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 Livedatalink. Nothing to install.
eia_natural_gas 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 eia_natural_gas 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 eia_natural_gas. 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.
eia_natural_gas is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue